We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28042 ☆ A M B ☆
    • 24,524 Posts
    Trying to duplicate a chunk, get this:
    Chunk doesn’t exist.
    in an otherwise empty right frame. However, the chunk is actually there, and shows up nicely after reloading the Resources frame. Rev 1822.

    Duplicating a snippet produced this
    Warning: Cannot modify header information - headers already sent by (output started at /Applications/MAMP/htdocs/jewishyou/manager/includes/header.inc.php:18) in /Applications/MAMP/htdocs/jewishyou/manager/actions/mutate_snippet.dynamic.php on line 51

    and a normal empty new snippet form.
      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
      • 22815
      • 1,097 Posts
      Contexts sound good; it sounds like Template Switcher works but we should point out somewhere that it is not compatible with caching and therefore shouldn’t be used on heavy sites. Multiple templates do make sense as multiple contexts, and I’m pleased to see caching is on a per-context basis. Future looks good.

      I am now sold on "Close Doc Manager" not being changed to "Cancel" because that would get confused with "Undo", but I still think removing the link makes sense. I guess what both buttons say is "Exit Without Saving Anything That Hasn’t Already Been Saved".

      This brings us to permissions - I’ve completed a review of the menu permissions vs what permissions are required to run the action.

      The Module list screen can be viewed (with limited functionality) by people with only Exec permissions, but the menu doesn’t let them see it. I guess that might be confusing as they can only get there by clicking Close Doc Manager, but this probably isn’t a big deal.

      The other screen where the menu is potentially hiding things that a user can actually see is Manage Resources - because the new Combined View subscreen includes modules, if someone has the ability to edit modules but not snippets, they could in theory see the modules sorted by category.

      While improving the logic of menu.php, I have left both of these as they are.

      What I *have* changed in light of the review is to not show page links if they aren’t actually usable, so:

      WAS:
      IF ’new_user’ OR ’edit_user’ { * * user_management_title }
      IF ’new_web_user’ OR ’edit_web_user’ { * * web_user_management_title }
      IF ’new_role’ OR ’edit_user’ { * * role_management_title }

      NOW:
      IF ’edit_user’ { * * user_management_title }
      IF ’edit_web_user’ { * * web_user_management_title }
      IF ’edit_user’ { * * role_management_title }

      Also, one minor error in the original allocation of permissions:

      IF ’settings’ { * * view_sysinfo }
      now
      IF ’logs’ { * * view_sysinfo }

      The menus are now, as per TobyL’s suggestion, built by collecting together the menu lines and outputting menus where they’re not empty.

      We still haven’t actually improved the Import / Export permissions, but as the new method adds the lines in PHP it is now much easier to comment out menu items that you want to omit, as the menu will automatically disappear.

      I’m posting the new file here because I can’t access my branch where I am now, and it’s just easier. If people could test it, particularly with different sets of permissions, that would be nice. (.txt added so I can post it here). Works fine for me.

      Next, languages...
        No, I don't know what OpenGeek's saying half the time either.
        MODx Documentation: The Wiki | My Wiki contributions | Main MODx Documentation
        Forum: Where to post threads about add-ons | Forum Rules
        Like MODx? donate (and/or share your resources)
        Like me? See my Amazon wishlist
        MODx "Most Promising CMS" - so appropriate!
        • 10487 MODX Staff
        • 1,535 Posts
        I’ve been testing the menu.php changes for about the last hour now and the changes seem absolutely fine to me. Great work, Paul! laugh

        My only suggestion is that if somebody doesn’t have ’Create Document’ permissions, then the ’New Document’ and ’New Weblink’ options are still visible - I think it would make sense to hide these, but for that change to be worthwhile then the toolbar above the tree menu would also need to be tweaked to hide the icons as well. That only tackles the most visible places where these options are available but, at least, it’s a step in the right direction.

        For instance, somebody with edit and save document rights but not ’create documents’ can still select the ’add another’ radio button when saving changes - it will pop up with a warning but doesn’t indicate whether that’s an error with saving the document or creating a new document (ugh!)

        Still, I’m digressing a bit ... as far as the scope of the changes that Paul did, then all is okay smiley
          Garry Nutting
          Senior Developer
          MODX, LLC

          Email: [email protected]
          Twitter: @garryn
          Web: modx.com
          • 25663 MODX Staff
          • 12,272 Posts
          Quote from: garryn at Oct 30, 2006, 02:40 PM

          My only suggestion is that if somebody doesn’t have ’Create Document’ permissions, then the ’New Document’ and ’New Weblink’ options are still visible - I think it would make sense to hide these, but for that change to be worthwhile then the toolbar above the tree menu would also need to be tweaked to hide the icons as well. That only tackles the most visible places where these options are available but, at least, it’s a step in the right direction.
          Agreed, and think we should do it right in both places. smiley

          For instance, somebody with edit and save document rights but not ’create documents’ can still select the ’add another’ radio button when saving changes - it will pop up with a warning but doesn’t indicate whether that’s an error with saving the document or creating a new document (ugh!)
          Unless we add another permissions wrapper around that bit too. smiley

          Still, I’m digressing a bit ... as far as the scope of the changes that Paul did, then all is okay smiley
          Thanks so much Paul for doing it and Garry for reviewing it. laugh
            Ryan Thrash, MODX Co-Founder
            Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
            • 10487 MODX Staff
            • 1,535 Posts
            Okay, menu.php update along with the additional ’new document’ permission wrappers committed to my personal branch in SVN as commit #1838 - ready to merge with trunk.

            update: done
              Garry Nutting
              Senior Developer
              MODX, LLC

              Email: [email protected]
              Twitter: @garryn
              Web: modx.com
              • 25663 MODX Staff
              • 12,272 Posts
              Jason’s merging Garry’s last batch of commits when he returns (including Paul’s permissions work). Jeff just completed updating TinyMCE to 2.0.8 with some new config parameters which hopefully resolves some questionable behavior (and coincidentally should work even better in Safari according to moxiecode!). I’ve just added a README file to the install package to tell people where to go for help and how to install.

              I think that leaves just a few key things before we get to our final release:
              [*] update Wayfinder to address http://modxcms.com/bugs/616
              [*] update Jot to final 1.0 release (due any day now I think)
              [*] update eForm to final 1.4.1 release (due Nov 1) 1857
              [*] addressing the last of the hard coded language strings reported in the bugtracker 1847
              [*] get partially/wholly updated translations in
              [*] get the installer to upgrade parameters, from prior versions of Tiny MCE (or give explicit instructions in the README file to rename existing assets directory and plugin) 1855
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                I returned my branch to the original files for document.parser.class.inc.php and save_content.processor.php since the business with document ID in the content of a weblink needs to be handled by the snippet if it uses the content for making a link. The makeUrl still needs to be called in the parser if a weblink document is loaded for parsing by a snippet, such as DropMenu. Wayfinder, which uses the content of a weblink to generate the link, will have to have its own makeUrl call.

                The addition to the installer, clearing locks on the manager, is still in my branch.


                update: in as of 1854, or thereabouts
                  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
                  • 30223
                  • 1,010 Posts
                  update eForm to final 1.4.1 release (due Nov 1)

                  Released,.. see this post for changes

                  Committed in 1857
                    • 25663 MODX Staff
                    • 12,272 Posts
                    Somethings that’s been in the back of my mind for a while is the textarea/text options for TVs. We’re changing the default behavior of them in 095 from previous releases. Evidence: http://modxcms.com/forums/index.php/topic,7066.msg60001.html#msg60001

                    Perhaps we should make raw text/textarea and text/textarea behave the same and introduce a new "escaped" text/textarea?


                    Addressed in 1858 with new HTML Entities output widget and making text/textarea and rawtext/rawtextarea behave the same. See the commit log for more details.
                      Ryan Thrash, MODX Co-Founder
                      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                      • 33372
                      • 1,611 Posts
                      Very good idea. Doing it the other way around is sure to cause people grief and confusion.

                      Addressed in 1858
                        "Things are not what they appear to be; nor are they otherwise." - Buddha

                        "Well, gee, Buddha - that wasn't very helpful..." - ZAP

                        Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options

                      This discussion is closed to further replies. Keep calm and carry on.