Debugging nocache errors

For questions and problems with the CMS core. This board is NOT for any 3rd party modules, addons, PHP scripts or anything NOT distributed with the CMS made simple package itself.
Locked
pinthenet

Debugging nocache errors

Post by pinthenet »

Can someone give me some pointers for debugging a module plse?
I created a modified Bookmarks module under release 0.11 to handle Links including images. It worked OK (although I occasionally got unexplainable nocache errors when editing, which disappeared after clearing the cache), but now with 0.12.1 I always get errors as soon as I include the module, even if the module doesn't have anything to output based on the selected filters (category etc)

The nocache errors appear before/after each {} on the page - eg {title}, {style} and of course any other {cms_module...} tags. All error values are the same apart form the sequence nr at the end

Running with debug shows no errors and if I compare with eg News or the new Bookmarks I can't really see any major differences in the template calls etc.

Also, although Preview works (except for the nocache errors), after apply/submit I often have a real page with no template or style until I clear the cache

Any tips appreciated

PS I use external templates - the bookmarks module at the time (1.3 I think) did not support them

John
pinthenet

Re: Debugging nocache errors

Post by pinthenet »

Oh well, in the absence of any tips I've decided to change my tactics and use a tag to format links and do without a module & database support.

Never mind  :-\
Ted
Power Poster
Power Poster
Posts: 3329
Joined: Fri Jun 11, 2004 6:58 pm

Re: Debugging nocache errors

Post by Ted »

Sometimes the output of the error will fall into a tag and the browser won't display it.  It's usually best to look at the html source and see if you can find an error somewhere.  It's almost always down at the bottom of the source.
pinthenet

Re: Debugging nocache errors

Post by pinthenet »

Thanks Ted
having made the change I realise that my module was a bit over the top for what I really needed, so it was a useful exercise anyway.

I'll remember your tip for the next experiment ::). I think I should take the time to study smarty a bit more closely before I try anything elaborate...
Locked

Return to “CMSMS Core”