Although I cannot say what led up to this situation as it seemed to just 'happen' after several weeks of not needing to use my 'Admin' access to my site (http://www.raffca.org.uk), attempting to gain access to the page displaying built-in tags (listtags.php) or the page that should display events (eventhandlers.php) results in the display of a totally blank page in my browser (I mean totally blank, with no code at all!).
I am at a total loss to think what might have led up to this, although I have checked permissions, etc, and they are exactly as they should be - and identical to those other files whose functions work! I have also upgraded to 1.6 in the last couple of days and find the problem persisting - and no other problems appearing at all.
If anyone has any ideas that I might pursue, I would be grateful for any assistance and/or advice. While the situation does not prevent the site from working (for guests or members of the associated YaBB Message Board) or from the general administration of the site as a whole, it is frustrating that a small part of the admin function has failed so totally - and I would like to try and understand why it happened.
[solved] Two items (Tags and Events) in Admin producing blank pages
[solved] Two items (Tags and Events) in Admin producing blank pages
Last edited by Jan Cobb on Mon Jun 29, 2009 1:07 pm, edited 1 time in total.
Re: Two items (Tags and Events) in Admin producing blank pages
that page AFAIK renders from the folder /plugins
You see any strange files in there?
Have you have added a UDT in there with error in code?
You see any strange files in there?
Have you have added a UDT in there with error in code?
ReneH 
A search will save you hours waiting for an answer!

A search will save you hours waiting for an answer!

Re: Two items (Tags and Events) in Admin producing blank pages
Thanks, reneh.
I had added 'variations' on 2 of the plugins (function.embed and function.ImageGallery) quite some time ago (long before the error manifested itself) and removing those files and reverting the one old file to its original name seems to have done the trick. What I don't understand is why it was okay for a while (a couple of months) before having a seizure, although it is possible that the upgrade 1.5.3 -> 1.5.4 might have been the start! Should I assume that changing or adding files in /plugins is verboten?
Jan
I had added 'variations' on 2 of the plugins (function.embed and function.ImageGallery) quite some time ago (long before the error manifested itself) and removing those files and reverting the one old file to its original name seems to have done the trick. What I don't understand is why it was okay for a while (a couple of months) before having a seizure, although it is possible that the upgrade 1.5.3 -> 1.5.4 might have been the start! Should I assume that changing or adding files in /plugins is verboten?
Jan