I recently migrated a website to a new server.

After moving all files and db's exactly, I could not restart XOOPS because of the error.

"Fatal error: Class 'XoopsLogger' not found in FILE on line X"

Here is the problem and how I solved it.

PROBLEM

You are most likely running a module that is trying to modify memory "by reference" instead of "by value" using the "&" symbol. In php4 this was supposed to be faster but php5 works differently with memory and now this has been deprecated. As of php 5.3 it may start to give you fatal errors. I found that to be the case here.

SOLUTION

Edit "FILE" from the error message. On line X, delete the inapropriate & symbol.

For example:

change $a =& $b to $a = $b

That's it. Should work!

I'm having the same problem.

php scripts don't execute in custom blocks in 2.4.4 .

For example:



Produces the code in a block.

I am not using protector. I don't think ... unless this is a new feature in 2.4.4 ...

Is there a security feature that prevents me from using php?

Only https

mainfile.php has the site as:https://thesite.com

It's the entire site. It is just that xoImgUrl still is configured to point tohttp://relativepathtoimages

this causes the standard security warning because the images are retrieved as unsecure content.

Perhaps I should upgrade to XOOPS 2.3.3 first - would that solve the issue?

I am on 2.0.18.1

Hi ... I think this is a smarty issue. I have a XOOPS website where the entire website is on https not http.

The images still load from the 'http' url and I am assuming that is because smarty fills in the http wherever 'xoImgUrl' is used.

I should be able to change that. Perhaps somebody knows the best way that I can cause 'https' to be inserted for all image urls in xoImgUrl

Cheers!