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

    David just informed me about this, and I’m totally sold out to this new alpha release.
    I don’t have time in reading all the forum topics right now, but I’ll keep an eye on the development of this recursive parser. When I got a chance, I will help with the development by finding bugs, fixing it and etc.

    Keep up the good work Raymond.

    Thanks to both Raymond and David (for telling me this wink)
      Wendy Novianto
      [font=Verdana]PT DJAMOER Technology Media
      [font=Verdana]Xituz Media
      • 6726
      • 7,075 Posts
      I have not been long without a reliable internet connection those past years, but I know what it feels like ! Glad I could help smiley

      As far as the new parser is concerned, I think it’s more of a beta than an alpha (but since I didn’t start testing, might be wrong).
        .: COO - Commerce Guys - Community Driven Innovation :.


        MODx est l'outil id
        • 32963
        • 1,732 Posts
        @David,

        Thanks for the heads up. I’ll try to add some more real world examples and try to simplify things a bit. I’m not really good at writting docs so I guess we could work together on finding ways to simply the various parts of the document.

        @Dimmy,

        Thanks for the feedback. There’s an option available on the parser that can be used to turn on/off debug mode. When it’s on it will show you the output of not only snippets but every tag that was proccessed by the parser. It would indeed be nice to have a System option to turn on/off system debug mode.

        @Wendy,

        Glad you see that you’re back online smiley
        Many thanks for the kind words.

        All the best and do keep up the good work.
          xWisdom
          www.xwisdomhtml.com
          The fear of the Lord is the beginning of wisdom:
          MODx Co-Founder - Create and do more with less.
          • 22815
          • 1,097 Posts
          Wow. This is amazing!

          Personally I think I’ll hold off any testing until it has been merged with the current parser version, because I assume that any changes to the normal parser are there for good reasons... but if I hit a wall with some coding and think "this would be so much easier if I had the recursive parser", it will be very tempting to give it a whirl!

          Certainly once this is brought up-to-date, I will pretty much switch to it and will be able to give any feedback then.

          I do think this should be included in a core release, not least because it will be a nightmare for the Repository to manage snippets etc if some of them need 0.9.2 + Recursive Parser and some need 0.9.5 Without Recursive Parser. Much easier if we can just say "Requires 0.9.5".

          I think this also means that 0.9.2 will never get full documentation - all examples will be changed to the new Recursive format!
            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!
            • 25663 MODX Staff
            • 12,272 Posts
            Bingo Paul, hence my hesitation to dive into a lot of documentation right now. smiley
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 6726
              • 7,075 Posts
              I finally started testing the new parser !
              My setup : testing local with MAMP - Apache 2.0.55, MySQL 5.0.19, PHP 5.1.2 - MODx 0.9.2.1 (rev 1005)

              Here are my findings :

              1) I have encountered a problem with DropMenu : I had to switch to the new syntax [[! ]] to make it work (for some reason it didn’t happen with other snippets).

              2) I tried the [[:IF-LOGIN? ... ]] it worked perfectly smiley

              3) I tried the [[:IF-GROUPS?... ]] worked great, as expected.

              4) [[:IF-ISSET? ... ]] worked great, as expected.

              5) [[:IF-ROLES ... ]] worked great, as expected.

              I’ll soon test the other.

              This is all very exciting it seems to work great. The only problem I encountered is my local server "hanging" : sometime the tag renders OK, no problem, fast load time and some other time it just "hangs" the system. Funny thing is, when the "hanging" happened I removed the conditionnal tag on a given page, save, try to reload the web page and bam, hanged again. I wondered if this could be a cache issue but I called the conditionnals uncached with [[: ..... !]] and it happened as well.

              I didn’t get time to test it on my dedicated server but my local testing config sometimes "hangs" (the dual proc is reaching peaks @ 1.13).
              Any idea why I have this problem ?

              Might be a config issue, but I am not too eager to try it on my dedicated server, my clients are hosted there I wouldn’t want the server to spiral out of control and have to restart...
                .: COO - Commerce Guys - Community Driven Innovation :.


                MODx est l'outil id
                • 32963
                • 1,732 Posts
                Hi David,

                Many thanks for giving it a try.

                I’ll have a look at the things you have mentioned. I think the problem is with processing the cached pages. It seems that the <html> is broken inside cached that’s why it might be hanging the browser. Uncached documents don’t seem to have a problem.

                As soon as I get some time I’ll have a look at it.

                Best regards,

                  xWisdom
                  www.xwisdomhtml.com
                  The fear of the Lord is the beginning of wisdom:
                  MODx Co-Founder - Create and do more with less.
                  • 6726
                  • 7,075 Posts
                  You’re welcome Raymond !

                  The new parser is so amazing and will be such a big step for MODx grin I have it on top of my priority list for testing... I guess right now everyone is busy with the new repository, but I am sure we’ll get some feedback very soon... I know Wendy will give it a test drive someday soon smiley

                  As I said, it might be my testing environment... I’ll try to make an install on my account @TextDrive, see if I have the same problem.

                  What could I do to help diagnose this ?
                  I remember we talked debug mode... Do I turn on MODx debug mode or does the parser have its own debug mode that I can activate ?

                  BTW, thanks for the quick response smiley
                    .: COO - Commerce Guys - Community Driven Innovation :.


                    MODx est l&#39;outil id
                    • 31337
                    • 258 Posts
                    Quote from: xwisdom

                    The anywhere you see the &pattern and &match parameters they all use php regex patterns.

                    Is it evalauting the pattern to match via a copy or via a reference? In either case what happens if someone uses a /e modifier on the regexp then?
                      • 32963
                      • 1,732 Posts

                      @David,

                      Quote from: davidm at Jun 30, 2006, 08:18 PM

                      What could I do to help diagnose this ?
                      I remember we talked debug mode... Do I turn on MODx debug mode or does the parser have its own debug mode that I can activate ?

                      Hi David,

                      You can enable parser debug mode by using $modx->enableDebug(true). For now you might want to do this inside the index.php. You could also do it from inside a Snippet but that’s not so much of a good idea.

                      Many thanks again.

                      @Victor,

                      Is it evalauting the pattern to match via a copy or via a reference? In either case what happens if someone uses a /e modifier on the regexp then?

                      Hi Victor,

                      The /e modifier is not support in the pattern matching tags. This is because /e modifier (according to the php manual) is only supported in the preg_replace() function. The new IF-MATCH and IF-BROWSER tags only perform regular expression matching using the preg_match php function.





                        xWisdom
                        www.xwisdomhtml.com
                        The fear of the Lord is the beginning of wisdom:
                        MODx Co-Founder - Create and do more with less.