0.9.5 test builds

Quote from: davidm at Aug 22, 2006, 08:45 AM

Some first test with the new parser tags with rev 1325 (...) Can someone confirm that ?

Anyone has tried out the new parser and can confirm the issues I raised ?

I haven’t had chance to even touch the envelope, let alone push the envelope when it comes to the new parser. Although I may use IF-BROWSER; it would let me have a site that validated by default.

Could you batch up some of the tests you have done and share it here either in a code block or as an attachment? It would be easier to start with something that is known to work, and to discover if any issues are environment related.

In fact the test I have done are either copy paste from the samples Raymond gave us in the parser’s doc, or "real use" on a live site I mirrored locally. I could provide the code I used of course but it would be out of the context of the website.

What I could do is give a go at trying out the new tags in the context of the "sample content" bundled with MODx, which would make it easier for everyone to re-use. In fact, that’s not a bad idea. I guess MODx users will need some samples of what can be done with the new parser, would be great to have this added to default content, no ?

But I’ll sure need help, since I am not anywhere near being able to figure out IF-ISSET, IF-EMPTY, IF-COMPARE without a least and example. Let alone IF-MATCH (requires regexp knowledge if I understood correctly).

Hi David, here is a simple IF-GROUPS call that works for me on the default site content (not very useful but it was a really simple test to get up and running). One thing I forgot to do first time round was to make sure that it calls it uncached, after that it worked fine.

I’ll post more test cases as soon as I get them - I’ve only just started playing with the new parser myself. Hope it helps in some way.

Thanks Garry, I did tried uncached but I might have slipped, not yet totally used to the new syntax I’ll make sure it wasn’t that...

Quote from: sottwell at Aug 22, 2006, 07:03 AM

The "Templates" page breaks badly, I suspect that the javascript is conflicting between the fancy javascript menu and the "themes". Or something.

I’ve definitely tracked it down to the javascript and the inner DropMenu call. I stuck a DropMenu call in the home page, and it did the same thing. I really don’t like that javascript menu.

The really odd thing is if I view source and copy/paste the ul block, there’s no problem.

Ok, what’s happening is that the second DropMenu call is re-assigning values in a global variable space. With the second DropMenu call a number of the classnames aren’t getting set.

And the javascript menu is still racking up the javascript errors at every mouseon and mouseoff of items with no submenus. Did I say that I don’t like the javascript menu?

Quote from: sottwell at Aug 24, 2006, 12:04 AM

And the javascript menu is still racking up the javascript errors at every mouseon and mouseoff of items with no submenus. Did I say that I don’t like the javascript menu?

that javascript menu needs to be customized in such way that each ’instance’ will have an id appended to the global variables.