We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32963
    • 1,732 Posts
    Adam,

    There’s a bug when editing Checkbox List TVs. It’s not saving the values
      xWisdom
      www.xwisdomhtml.com
      The fear of the Lord is the beginning of wisdom:
      MODx Co-Founder - Create and do more with less.
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      If it were another optional plugin, maybe. I would hate to see QE turn into BE (Bloated Editor)! I, personally, have no desire to create web sites graphically. I’ve used FrontPage and Dreamweaver. Then I spent as much time editing the horrendous HTML they produced as I would have writing the HTML myself. I like QE for what it does...quickly edit the current document in situ. That is the whole idea behind MODx that I like; it’s light and quick to work with and getting more modular almost by the day.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 25663 MODX Staff
        • 12,272 Posts
        Susan, I don’t think the little additions would ever come close to matching DW/FP/whatever. And the implications of creating new docs in the front end bear very careful consideration indeed.

        The only thing that might not be easy or even the right thing to do is to in fact create docs from the front end, but all the other functions defintely bear merit in my book... along with being able to edit "hidden" meta content and IDs on certain elements (like the body tag).
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 1764
          • 680 Posts
          Quote from: xwisdom at Aug 25, 2005, 12:55 AM


          a.QuickEditLink{
          cursor:pointer;
          }


          Yea, I caught that a little too late. I’m so bad at remembering to chek IE. I hope to make some changes this week and I’ll release this change along with some improved resizing and other things.
            • 1764
            • 680 Posts
            Quote from: rthrash at Aug 25, 2005, 01:27 AM



            • Go to Manager
            • Hide QE links (or Show if Hidden)
            • End QE Session (logout of manager in reality)

            Later, we could also add:

            • Move Document
            • Delete Document
            • Create Document Here
            • Create Folder Here
            • Unpublish Document
            • Show unpublished Documents

            I’ve thougth it would be a good idea to have the option to enable a toolbar like this for a little while now. I like the idea of having Go to manager and logout, I hadn’t thought of that.

            Delete would be the simplest functionality to implement. Unpublish would be easy too. Move would be a little tricky but I think I have a good idea that wouldn’t be too difficult to do. More like a copy and paste so we don’t have to deal with the tree. Create document shouldn’t bee too difficult either as long as you don’t want to get too deep into permissions and settings. I think it would be best to have a simple create document and just have it give it default attributes with a Blank Page title that you could then change. My feeling on folders is why give them the option? If a document has children, it’s a folder, if not it isn’t, seems like it could be handled transparently by the backend. Create/Delete documents could be responisble for setting the folder attribute of it’s parent.

            And that leaves us with publish document and show unpublished document. Here’s the catch, we’ll have to make a small change to the core so that logged in users can see unpublished documents. Either that or a plugin to allow an override. Personally, I think that manager users need to be able to see unpublished documents as a standard feature, that way when you click an unpublished document in the manager you don’t get the 404 page but you can actually see what it is that you are going to be editing.

            Maybe I’m not understanding what you mean by show unpublished documents but I don’t see how QuickEdit can do this. I think this would have to be an option in a menu snippet. Our site has a menu snippet that shows greyed out links for unpublished documents if the user is logged in.

            Another thing I’d like to throw into the mix is a drop down list of all of the TVs you have access to on the page. That way you could easily edit hidden elements without having to put the QE tags in yourself and you could turn off the inline tags and use the header only if you prefer. Show/Hide QE links could be stored in a cookie so that it could remember your preferences between sessions.

            I’m considering delving into AJAX for some of this. I haven’t done any thing with AJAX yet but I’ve done similar things in the past so I don’t think the learning curve will be too steep.

            What do you think?

            P.S. I’ll look into that checkbox issue and see if I can get an update out this weekend sometime. I’m pretty swamped now, but I’m hoping to get some free time to work on this this weekend.
              • 34162
              • 1 Posts
              Great idea!

              Ajax is a perfect bit for this purpose.

              It would be nice to have a feature in QuickEdit to set basic or advance feature so that if one prefer a simple QuickEdit then that is all they will get but if they want the work then turn the the advance mode to see everything that was talk about in this thread.

              In Mambo, when I click on the "edit" icon, I am able to change title, category, intro, main text, image attributes, publishing attributes, meta data attributes, etc. and If I set to have no editor then I will see a textarea in place of WYSIWYG editor.

              It is very standard set up feature now a day for frontpage editing.

              It would be cool if Modx and QuickEdit can do similar things like that!
                • 1764
                • 680 Posts
                Quote from: chanh at Aug 25, 2005, 08:37 AM

                Great idea!

                Ajax is a perfect bit for this purpose.

                It would be nice to have a feature in QuickEdit to set basic or advance feature so that if one prefer a simple QuickEdit then that is all they will get but if they want the work then turn the the advance mode to see everything that was talk about in this thread.

                In Mambo, when I click on the "edit" icon, I am able to change title, category, intro, main text, image attributes, publishing attributes, meta data attributes, etc. and If I set to have no editor then I will see a textarea in place of WYSIWYG editor.

                It is very standard set up feature now a day for frontpage editing.

                It would be cool if Modx and QuickEdit can do similar things like that!


                We’ll definitely have some sort of a method of turning the advanced QE interface on and off.

                I agree with Susan that we shouldn’t let it get to bloated but I think that having the option to turn on advanced features would be a nice option for power users.
                  • 25663 MODX Staff
                  • 12,272 Posts
                  Adam, any chance we could get an on-off switch and maybe a couple of the other things early next week? It might be really nice to be able to set the web-user groups from the front end as well for quick fixes for private-access sites from the front end.

                  Don’t worry so much about the Ajax stuff until the TP4 is released internally as it will make that much easier out of the box... VERY soon. smiley

                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 1764
                    • 680 Posts
                    Quote from: rthrash at Aug 25, 2005, 09:42 AM

                    Adam, any chance we could get an on-off switch and maybe a couple of the other things early next week? It might be really nice to be able to set the web-user groups from the front end as well for quick fixes for private-access sites from the front end.

                    Don’t worry so much about the Ajax stuff until the TP4 is released internally as it will make that much easier out of the box... VERY soon. smiley



                    It’s possible, but I’m not going to make any promises.

                    I have a lot of things going on right now and I hope things will quiet down a bit next week. I have one client that called me on Monday wanting a site up before Saturday (remember I have a full time job on top of this) and I have a sneaky suspicion that they’re waiting to throw another rush job at me as soon as this one is done. If not, I should have the time to get an update out.