Issue With View Recent Posts

5 replies [Last post]
Miffy
Miffy's picture
Offline
Joined: 19/03/2005

Just logged in this morning (about 5 minutes ago) and got the following error when I clicked Recent Posts. It didn't seem to appear anywhere else, nor make the page not work, but I'm guessing it should be fixed at some point.

As ever I'm on Mac OS X using Safari 4.0.5 .

Edit: It also throws one up when uploading files (error2)

Edit Edit: Also when creating new forum post there was a massive one, which seemed to be a repetition of the others. It was too big to screen dump, but the error was in reference to line 150 and mentioned smilies.

AttachmentSize
error.jpg24.38 KB
error2.jpg16.69 KB
__________________

Leeds Rock Society's 'Most Overseas Member' 2005-06

Leeds Rock Society General Committee 2006-07

Leeds Rock Society Grand Mistress Of The Ball 2007

Leeds Rock Society Little London Bravery Award 2006-07

Hunter
Hunter's picture
Offline
Joined: 26/09/2005

Its probably some form of update that hasn't been assimilated by drupal yet.

__________________

They say only the good die young. If that works both ways, I'm immortal.
The First Rule of Tautology Club is the first rule of Tautology Club.

iostream
iostream's picture
Offline
Joined: 25/09/2003

I just got off the phone with charles, and he updated the operating system last night to the latest Ubuntu LTS. So PHP has just been upgraded. The version of Drupal we are on now is getting on a bit so there are bound to be issues like this starting to pop up*.

The big question is why is a deprication warning being thrown out to all and sundry...

It appears that error reporting was set to be both screen+log rather than just log.

People should no longer see any of these errors, so if they are seen, let me know.

* I am slowly working on building the site for the next version of Drupal, so that issue is being worked on.

talkToTheHat
talkToTheHat's picture
Offline
Joined: 10/10/2002

Because drupal reports errors rather than silently fails, and the Ubuntu PHP setup reports deprecation errors by default.

This applies to version six, but...
http://technomancer.me.uk/blog/enabling-php-error-messages-drupal

__________________

I am not a Legend, I'm just in exile for playing keys.

iostream
iostream's picture
Offline
Joined: 25/09/2003

Errors should only be admin-visible in a production environment. Especially non-fatal errors, which deprication errors certainly are.

I have just looked into this and Drupal 5 does not support php 5.3.

It appears Drupal 6 does in core from version 6.14, however it appears that a whole lot of contributed modules don't and are not required to support it for the lifetime of Drupal 6.

Thus I would like to request that you look into rolling back to the php 5.2 branch until Drupal 8* comes out.

http://drupal.org/requirements
http://drupal.org/node/360605

* My assesment of the way that Drupal does not wait for any contributed module, no matter how popular (to be fair, their reasoning and philosophy in this is sound) means that from my judgement, the rocksoc site should not upgrade major version numbers until the used major version number is no longer supported then it shall move over to the next version (not jump versions). This is to allow for optimum stability in both core and contributed modules. Thus the roll-over to D6 will happen either shortly before or soon after D7 is released (i.e. I am beginning preparations (starting with a new theme) now).

talkToTheHat
talkToTheHat's picture
Offline
Joined: 10/10/2002

As posted, drupal has a knob to twiddle over whether it failed silently. D6 defaults to silent and deadly.

I'd love a module that ticketed the errors, and logged them internally and to apache's error log and went, oops, I just broke, tell an admin 20105250353-t681. But that's beside the point.

...much swearing at php...
...php5.2 from karmic installed...

__________________

I am not a Legend, I'm just in exile for playing keys.