We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19164
    • 1,215 Posts
    It is good that you continue your work on this super plugin.

    I just download plugin and first that i saw- when im edit any of plugin, code of MM plugin is posted after textarea.

    I found that text in plugin comments "not have <?php at the beginning or ?> " cause that strange behavior in my case.

    MODx 0.9.6.1p2
      DirectResize 0.9 beta. PHPThumb, sets of configurations, configuration, binded to specific path. No backward compatibility. | DirectResize 0.9. PHPThumb, наборы параметров, параметры, привязанные к определенным путям. Без обратной совместимости.

      Unfortunately, DirectResize project is closed. If you want to continue development, PM me for access to project page on Google Code. К сожалению, проект DirectResize закрыт. Если вы желаете продолжить разработки, обращайтесь через ПМ для получения доступа к репозиторию на Google Code.

      [PLUGIN] DirectResize - as Maxigallery but for single images :: Download :: [url=http://modxcms.com/forums/index.php/topic,21490]
      • 21056
      • 327 Posts
      Quote from: Metaller at Jul 02, 2008, 10:11 AM

      It is good that you continue your work on this super plugin.

      I just download plugin and first that i see - when im edit any of plugin, code of MM plugin is posted after textarea.

      I found that text in plugin comments "not have <?php at the beginning or ?> " cause that strange behavior in my case.

      MODx 0.9.6.1p2

      There should be no <?php / ?> in the plugin.txt

      Did I leave one in?
        Author: ManagerManager plugin - customise your ModX manager interface

        Rckt - web development, Sheffield, UK
        • 19164
        • 1,215 Posts
        Yes, in plugin.txt.
        // The file contains some example rules (which you can copy to the chunk - although the chunk should not have <?php at the beginning  or ?> at the end
        $config_chunk = 'mm_rules'; 


        And one question - what is an interesting idea about manipulations on TV editing page? Did we can add new TV types? I saw that all code is commented.
          DirectResize 0.9 beta. PHPThumb, sets of configurations, configuration, binded to specific path. No backward compatibility. | DirectResize 0.9. PHPThumb, наборы параметров, параметры, привязанные к определенным путям. Без обратной совместимости.

          Unfortunately, DirectResize project is closed. If you want to continue development, PM me for access to project page on Google Code. К сожалению, проект DirectResize закрыт. Если вы желаете продолжить разработки, обращайтесь через ПМ для получения доступа к репозиторию на Google Code.

          [PLUGIN] DirectResize - as Maxigallery but for single images :: Download :: [url=http://modxcms.com/forums/index.php/topic,21490]
          • 21056
          • 327 Posts
          Quote from: Metaller at Jul 02, 2008, 10:33 AM

          Yes, in plugin.txt.
          // The file contains some example rules (which you can copy to the chunk - although the chunk should not have <?php at the beginning  or ?> at the end
          $config_chunk = 'mm_rules'; 

          Ah, even though they’re commented out, the <?php tags are probably throwing it. Does it work better if you take that comment out?

          Quote from: Metaller at Jul 02, 2008, 10:33 AM

          And one question - what is an interesting idea about manipulations on TV editing page? Did we can add new TV types? I saw that all code is commented.

          I’ve been experimenting with using the TV definition interface as a way of applying widgets (e.g. colour picker, tags, etc) so they appear on the TV type list, instead of doing them through code. That works -- BUT you lose the flexibility of being able to apply them only to certain roles or templates, or supplying other options, so I’ve pretty much decided against it. I also hide the deprecated items off that list because they annoy me!

          There’s other bits of work in progress code (commented out) for manipulating the top tabs (I’ll probably do something with this is 0.4) and for changing the ’info’ page for a document (the one you get when you click on a document, before you edit it) so if a field is hidden it is also hidden from there. But I think this will not be possible, due to the Modx event architecture of that page.
            Author: ManagerManager plugin - customise your ModX manager interface

            Rckt - web development, Sheffield, UK
            • 21056
            • 327 Posts
            Quote from: gbryanmiller at Jun 27, 2008, 02:57 PM

            If not, is there another way to do this without modifying the core code?
            I have found a way of manipulating this with Javascript (not modifying the core code), but it is a long way from being working. If I can work it out fully it may be in a future release.
              Author: ManagerManager plugin - customise your ModX manager interface

              Rckt - web development, Sheffield, UK
              • 19164
              • 1,215 Posts
              Quote from: ncrossland at Jul 02, 2008, 10:43 AM
              Ah, even though they’re commented out, the <?php tags are probably throwing it. Does it work better if you take that comment out?

              Yes, it works as it must when i remove this tag.

              I see that you have great plans on the future and i hope that this plugin will be important in 0.9.7 or may be manager of the new MODx will be more flexible.

              But now it is one of the best application for MODx. Must have for any of completed site.
                DirectResize 0.9 beta. PHPThumb, sets of configurations, configuration, binded to specific path. No backward compatibility. | DirectResize 0.9. PHPThumb, наборы параметров, параметры, привязанные к определенным путям. Без обратной совместимости.

                Unfortunately, DirectResize project is closed. If you want to continue development, PM me for access to project page on Google Code. К сожалению, проект DirectResize закрыт. Если вы желаете продолжить разработки, обращайтесь через ПМ для получения доступа к репозиторию на Google Code.

                [PLUGIN] DirectResize - as Maxigallery but for single images :: Download :: [url=http://modxcms.com/forums/index.php/topic,21490]
                • 21056
                • 327 Posts
                Quote from: Metaller at Jul 02, 2008, 12:04 PM

                Quote from: ncrossland at Jul 02, 2008, 10:43 AM
                Ah, even though they’re commented out, the <?php tags are probably throwing it. Does it work better if you take that comment out?

                Yes, it works as it must when i remove this tag.

                I see that you have great plans on the future and i hope that this plugin will be important in 0.9.7 or may be manager of the new MODx will be more flexible.

                But now it is one of the best application for MODx. Must have for any of completed site.
                Thanks, glad you find it useful. To me, making the Manager just as flexible as the front-end is really important, particularly when you have clients of differing levels of technical ability using them. One of the appeals of Modx is that the manager is very straightforward; this makes it possible to make it more so.

                I hope it will be possible to do some of the things natively in 0.9.7. As I understand, the manager will be easier to override and customise because of being Ext JS based, but I will liaise with the dev team to find out more.

                In any case, I wouldn’t even begin to try and port it until 0.9.7 makes beta status, as while in alpha so many things may change.
                  Author: ManagerManager plugin - customise your ModX manager interface

                  Rckt - web development, Sheffield, UK
                  • 30497
                  • 245 Posts
                  not sure if you would consider it a bug, or what exactly is happening:

                  With the latest ManagerManager, If I create a chunk mm_rules for adding rules in the Manager, but then I leave that chunk blank, I get the following MODx parse error when trying to create a new document:
                  « MODx Parse Error »
                  MODx encountered the following error while attempting to parse the requested resource:
                  « Execution of a query to the database failed - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND tvs.name IN ('blogTags')' at line 1 »
                        SQL: SELECT name FROM `babelaud_babela`.`modx_site_tmplvars` tvs LEFT JOIN `babelaud_babela`.`modx_site_tmplvar_templates` rel ON rel.tmplvarid = tvs.id WHERE 1=1 AND rel.templateid = AND tvs.name IN ('blogTags')
                        [Copy SQL to ClipBoard]
                   
                  Parser timing
                    MySQL: 	0.0011 s	(4 Requests)
                    PHP: 	1215408969.0572 s	 
                    Total: 	1215408969.0583 s


                  adding some example text to the chunk prevents this parse error.
                    • 21056
                    • 327 Posts
                    Quote from: towerofbabel at Jul 07, 2008, 12:57 AM

                    not sure if you would consider it a bug, or what exactly is happening:

                    With the latest ManagerManager, If I create a chunk mm_rules for adding rules in the Manager, but then I leave that chunk blank, I get the following MODx parse error when trying to create a new document:
                    « MODx Parse Error »
                    MODx encountered the following error while attempting to parse the requested resource:
                    « Execution of a query to the database failed - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND tvs.name IN ('blogTags')' at line 1 »
                          SQL: SELECT name FROM `babelaud_babela`.`modx_site_tmplvars` tvs LEFT JOIN `babelaud_babela`.`modx_site_tmplvar_templates` rel ON rel.tmplvarid = tvs.id WHERE 1=1 AND rel.templateid = AND tvs.name IN ('blogTags')
                          [Copy SQL to ClipBoard]
                     
                    Parser timing
                      MySQL: 	0.0011 s	(4 Requests)
                      PHP: 	1215408969.0572 s	 
                      Total: 	1215408969.0583 s


                    adding some example text to the chunk prevents this parse error.
                    have you left the default example rules in the mm_rules.inc.php file?

                    If the chunk is empty / missing, it will look in this file automatically.
                      Author: ManagerManager plugin - customise your ModX manager interface

                      Rckt - web development, Sheffield, UK
                      • 30497
                      • 245 Posts
                      Quote from: ncrossland at Jul 08, 2008, 03:12 AM

                      Quote from: towerofbabel at Jul 07, 2008, 12:57 AM

                      not sure if you would consider it a bug, or what exactly is happening:

                      With the latest ManagerManager, If I create a chunk mm_rules for adding rules in the Manager, but then I leave that chunk blank, I get the following MODx parse error when trying to create a new document:
                      « MODx Parse Error »
                      MODx encountered the following error while attempting to parse the requested resource:
                      « Execution of a query to the database failed - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND tvs.name IN ('blogTags')' at line 1 »
                            SQL: SELECT name FROM `babelaud_babela`.`modx_site_tmplvars` tvs LEFT JOIN `babelaud_babela`.`modx_site_tmplvar_templates` rel ON rel.tmplvarid = tvs.id WHERE 1=1 AND rel.templateid = AND tvs.name IN ('blogTags')
                            [Copy SQL to ClipBoard]
                       
                      Parser timing
                        MySQL: 	0.0011 s	(4 Requests)
                        PHP: 	1215408969.0572 s	 
                        Total: 	1215408969.0583 s


                      adding some example text to the chunk prevents this parse error.
                      have you left the default example rules in the mm_rules.inc.php file?

                      If the chunk is empty / missing, it will look in this file automatically.

                      yes, mm_rules.inc.php is untouched - perhaps I had a problem with the path to that file? I’ll check.

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