0.9.5 test builds

I got the folloing error when I added the debug snippet.

Fatal error: Call to undefined function: listtab() in /home/httpd/vhosts/hilverda.eu/httpdocs/assets/cache/siteSnippets.cache.php on line 4260

I deleted the file eand dit it again and dit a site refresh but still the same error

when hoovering the icons just above the document tree the whole tree shifts 3 pixels the container that holds the icons lookst to small.

some images are missing

I got the folloing error when I added the debug snippet.

Fatal error: Call to undefined function: listtab() in /home/httpd/vhosts/hilverda.eu/httpdocs/assets/cache/siteSnippets.cache.php on line 4260

I deleted the file eand dit it again and dit a site refresh but still the same error

when hoovering the icons just above the document tree the whole tree shifts 3 pixels the container that holds the icons lookst to small.

some images are missing

Well, I gave the debug snippet a test and alas, on my setup, all I get is a blank page (for some reason, I just can’t get error messages with the new parser). But, the reason the snippet fails is because the listtab() function declaration needs to be above where it is first called ie. at the top of the snippet.

On the subject of images, can you post a list of the ones you’ve found to be missing? I’ve found a few as well (in the Event Log) so it would be good to try and get them fixed.

The input boxes in "Create/ edit template" do not align.

in "Manage files" the icon for the file: ht.access is missing it looks in /manager/media/images/icons/context_view.gif while this image is displayed for the other files is located in /manager/media/style/MODx/images/icons/context_view.gif and works fine.

the bottom button bar plugin was only enebled for: OnChunkFormRender while it needs all formrender option set for it to wok there aswell.
the images for this plugin point to: /manager/media/style/images/icons/save.gif this is not right, it should be:media/style/MODx/images/icons/save.gif

I’d really like to get a public beta out ASAP, but I’m a bit concerned by the caching system in the current trunk after sitting on it for a few days. The problem lies in two areas:

1) All the snippets, whether used or not, are copied into the cache, comments and so forth included. This seems to be a bit of bloat that could lead to performance issues potentially.

2) If one snippet is not right and errors, whether it’s used or not, it takes the whole site down. I personally experienced this issue with the Membercheck snippet on a localhost install (it was not compatible with PHP4 I was testing with).

The first issue is not really a show stopper, but it would seem that it could negatively impact memory requirements particularly since I think those files have to be read on every page load (not sure here). The second issue though seems to be a show stopper for a public beta.

Sounds like a killer to me.

Snippet caching is a HUGE problem. It should be possible for users to test new snippets on a private part of a live site without risking the whole site going blank.

How essential is snippet caching to the Recursive Parser? If it can be disabled, then I’d be in favour of releasing at least a low-key "Preview" edition.

Hi,

Back in the days the snippets where stored as strings inside the cached file where they would then be executed using eval().

If needs be the caching system can be reverted to the ealier version and a fix be made to the parser to resume eval()s for the short term. I have a long term long solution but that will not be ready in time for the release of 0.9.5.

Ah, so to accomodate the fact that a snippet can be called within a snippet, two things changed:

1) the location of cached snippets (was in cached document, now separate file)
2) how they are stored (was strings, now not)

So we may only need to change 2) and not 1) ?

My preference would be for the cache to by default use strings and eval, as this avoids the blank-site issue with untested / badly-formed snippets. But perhaps there could be a configuration option to not use strings, which would give a speed boost at the expense of requiring all snippets to be perfect. (Changing this would reset the cache). This would add an optimisation phase to serious/large sites : "remove snippets that are not being used, switch snippet caching method to Pure".

Also:
Does anyone have a 0.9.5 manager available to the public that they can point
Amok, the guy whose IE crashes on ’Edit’ at, just so we can see if his issue is resolved there?

The current Trunk is effectively dead due to the caching system changes... Quote from: xwisdom at Aug 28, 2006, 05:10 PM

Back in the days the snippets where stored as strings inside the cached file where they would then be executed using eval().

If needs be the caching system can be reverted to the ealier version and a fix be made to the parser to resume eval()s for the short term. I have a long term long solution but that will not be ready in time for the release of 0.9.5.

FYI, the current trunk is effectively dead without reverting the caching system... :/ Another bug with the caching system is that it dies with snippets or plugins that include lines that begin with things like "// <?php" or "// ?>".