I’d like, in short, to see the first post of the thread link to lots of other threads - ideally about specific issues, but not necessarily. Hmmn. Just volunteered myself for a lot of work.
MODX Staff
I’ve made a few small changes in the Upload snippet so that it correctly parses the nested tags, as long as the bbcode equivalents are used to define them. The styling still needs to tweak as it currently doesn’t handle nested tags very well - I will look at this tomorrow.
I saw that in the bb-code there is an option to display snipptes [snippet] and [usnippet] but what if you want to call a snippet insite a snippet? like [!DropMenu? &id=[[SectionRoots]]!] ? it wil be getting even more fun to pars snippetcals when people are starting to use the new recursive parse Raymond made tahn all kind of funny combinations are posible.
Any non-bbcoded snippet/tv/chunk calls will now be stripped out of the Description field (they already were for most of the fields, that one must’ve slipped through the net)
adding [!DropMenu!] to the Description field does nothing it display’s [!DropMenu!]
but adding [[DropMenu]] to the Description field wil result in a nice menu
MODX Staff
« MODx Parse Error » MODx encountered the following error while attempting to parse the requested resource: « PHP Parse Error » PHP error debug Error: mysql_num_rows(): supplied argument is not a valid MySQL result resource Error type/ Nr.: Warning - 2 File: /home/httpd/vhosts/modxcms.com/httpdocs/manager/processors/cache_sync.class.processor.php Line: 78 Line 78 source: $limit_tmp = mysql_num_rows($rs); Parser timing MySQL: 0.1155 s s (37 Requests) PHP: 0.3432 s s Total: 0.4587 s s
Just need to fix the navigation folder icons, which are botched at the moment then I say we unload it on the general forums as quickly as feasible thereafter.
The demo site is interesting - each version of a resource seems to have its own tags, and clicking ’ajax’ for example pulls up all the previous versions of a resource : http://modxtest.muddydogpaws.com/resource_listing.html&tags=ajax - but the link goes to the latest version.
Is that intended behaviour? I’m actually kinda glad people are directed to the latest version but I would much rather just see the latest releases. There is a theoretical issue if TunaCatcher 1.5 has the tag "Dolphin-friendly" but TunaCatcher 1.6 doesn’t - so perhaps it should show the most recent release that matches the tag?
Perhaps this also ties in to the needed ability to mark a snippet version as "dead"?
MODX Staff
I’ve been looking at this today - it appears the synccache class is losing the database information somewhere along the line and resulting in the query failure. It’s baffled me why this has only just happened, but it seems to be a persistant error now regardless of what I do.
I tryed to edit my reopsitory post but it gave me this error;
The intended behavior I was questioning was the listing on the tag search results screen of previous versions.
I am concerned that what will happen is that you’ll click on AJAX and half the results will be the same resource.
If people who actually want the older version have to click on the link to the latest release and then scroll down to the older versions, there seems no point listing the older versions separately on the search results page.
My point about specific versions being dead was that this could be used as a filter so that the tag search results could know not to show the older versions.
There are however many times that two versions are "alive" at the same time, for whatever reason. PHP4 & PHP5; OtherExample 0.9.5 and OtherExample 1.0 Beta might both be supported for various reasons, and in those instances there may be merit in both appearing in search results.
This discussion is closed to further replies. Keep calm and carry on.