Serendipity Forums

I got this message instead of a random picture of a Menalto-Gallery2

Notice: in /home/.../bundled-libs/PEAR.php on line 848

line 848:
trigger_error($this->getMessage(), $this->level);

Normally a picture is shown, I got this message only once with http://hackerart.at/

Hi!

This error usually happens if the PEAR library was not able to connect to a specific server. Many plugins use the PEAR library, also the menalto-gallery, as it seems.

Currently we have found no way around this sorts of messages, as they come from quite deep of the PHP core and are passed on by PEAR.

Best regards,
Garvin

I would like to like to let you know, that there was no chance to get my test blog (not hackerart) work again with this bug. First I disabled "rewrite" and enabled it again, and the blog worked again. A short time later, there was the error again and I could not solve the problem as I did before. I had to delete the Plugin "Zufälliges Bild aus einer Menalto-Gallery" and it worked again, when I added this plugin again, the sidebar was not displayed again.

Some problems I got, when I added a plugin twice. Some plugins are not displayed as installed, even if they can be installed only once. Maybe there is a relationship with this bug?

With Hackerart the plugin "Zufälliges Bild aus einer Menalto-Gallery" seems to work, so I do not change this at the moment. Do you think the plugin "Unified Sidebar Image Display" has less problems with PEAR.php?

Which info would you like to have, if I get this error again and the error is repeatable?

The "Unified Sidebar Image Display" uses the same code as the Gallery sidebar... The idea is to remove the single plugins at a later date (so that there are fewer plugins in Spartacus).

So changing plugins isn't likely to solve your problem. The problem actual comes from the Pear module being unable to connect to the Gallery server. The error means there is either a network problem between the servers, or the server is down (or too busy to handle a request).

There are several ways around this problem. One would be to cache the data from requests for a period of time (so that the Gallery server isn't so busy). Obviously this won't help if the Gallery server goes down, and it means images won't rotate as often. The other way would be to host both packages on the same server and write an entirely new plugin to access the Gallery database directly. Neither of those are great solutions, but I think those are the best two options when using two different software packages.

A third option might be to use a HTML nugget with an iframe, but most people aren't especially happy with that (it tends to look a little clunky).

If I get around to adding the other Gallery2 display options to the Unified Sidebar plugin I will look at adding a caching system to it (the built in sidebar display plugin already supports caching, so I should be able to use some of that code relatively easily.

Caching would be fine for _me_ since I do not upload new files every day, maybe I upload every month. The blog is on the same server, but maybe another account is used, so the gallery could have a different Home-Directory. At the moment the blog and the gallery use the same home-dir, but this can change, if my hoster has to much problems. Today the mysql-server was down for a short time, but I didn't get this error when I tried a reload or opened another link in the blog. The whole page was not loaded. Maybe there could be an option, if caching should be used.

Also it would be a lot better, if the error-message can be replaced with a message like "server cannot be reached". Visitors get confused with complex error notices and think s9y has a bug, although the problem is the server.