English (United Kingdom)
Jms Multi Site, formerly joomla multisite.
Create, share multiple joomla sites in few clicks !
Message
  • EU e-Privacy Directive

    This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

    View e-Privacy Directive Documents

Welcome, Guest
Please Login or Register.    Lost Password?

[SOLVED] Fatal error on slave sites
(1 viewing) (1) Guest
Go to bottomPage: 1
TOPIC: [SOLVED] Fatal error on slave sites
#12365
[SOLVED] Fatal error on slave sites 9 Years, 10 Months ago Karma: 0
Hi,

We have currently a running master website with around 60 slave sites. We now want to update our installation, so we copied the whole site to a test server. Joomla and Multisites are successfully updated, however all the slave sites now have a fatal error:

Code:

Strict Standards: Non-static method Jms2WinFactory::import() should not be called statically, assuming $this from incompatible context in /var/www/site/files/components/com_multisitescontent/router.php on line 50

Fatal error: Cannot redeclare class ContentRouter in /var/www/site/files/components/com_multisitescontent/multisites.router.php on line 454



Live environment:
PHP 5.3.10-pl0-gentoo
Joomla 3.1.1
Multi Sites: 1.3.15 - basic
Multi Sites Content: 1.2.01

Test environment
PHP 5.5 / PHP 5.4
Joomla 3.3.6
Multi Sites: 1.3.41 - basic
Multi Sites Content: 1.2.02

I have tested the site on the live server as well to see if a lower PHP version ignored the error, but no luck.

There is no difference between the router.php of the latest multi sites, compared to the current running on the working website.

What could be the cause of this issue?
joomblocks
Fresh Boarder
Posts: 8
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2015/03/25 09:26 By joomblocks.
The administrator has disabled public write access.
 
#12376
Re: Fatal error on slave sites 9 Years, 10 Months ago Karma: 54
First, the fact that you did a backup on a test environment is an excellent practive that we recommend apply in our "Apollo 13" procedure.

Concerning the upgrade, I first notice an incompatibility error because the "Multi Sites Content" version 1.2.x is NOT compatiblit with J3.2 or higher.
You need the version 1.3.x to be compatible with J3.3

Concerning the PHP Strict "import()" error, there is NO solution for this one to be removed. We use a facility present in PHP that force us to keep it "not static".

Concerning the fatal error, this is an error due to the "Multisites Content" version 1.2.x that is NOT compatible with J3.3
You need to buy the latest version 1.3.x

Once you will have upgraded your master, don't forget to go in the back-end of each slave site to perform the extension mangager / database => Fix button
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#12402
Re:Fatal error on slave sites 9 Years, 9 Months ago Karma: 0
Hi Edwin,

We have bought the "Multi Sites Content" version 1.3 yesterday and updated our Joomla version from 3.1.1 to 3.4 on a test server. All extensions are now updated to the latest version. However we get a wsod, without errors being written to the error log (error reporting is set to maximum).

I have narrowed it down to Multi Sites Article Sharing menu items. If all menu items using article sharing are disabled the site works fine, the moment an article sharing menu item is enabled the site displays the wsod.

Live environment:
PHP 5.3.10-pl0-gentoo
Joomla 3.1.1
Multi Sites: 1.3.15 - basic
Multi Sites Content: 1.2.01

Test environment
PHP PHP 5.4
Joomla 3.4
Multi Sites: 1.3.45 - basic
Multi Sites Content: 1.3.04

If I look at the change history the main Multi Sites component is updated to work with Joomla 3.4, but do we have to wait for a new release of the Article Sharing extension?

Regards, Emiel
joomblocks
Fresh Boarder
Posts: 8
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#12405
Re:Fatal error on slave sites 9 Years, 9 Months ago Karma: 54
For the moment, we don't know any error with the latest article sharing v1.3.04 with J3.4.x.

Did you tried to purge the "article sharing" in the back-end in case where some J3.1.1 would remain present.

If you don't have any error message, the only solution would be to debug on your environment to identify the peace of code that would have a problem under J3.4.x

To be able fixing something, we need to be able reproducing it.

If you have the possiblity to run a PHP debugger on your test environment, perhaps that you could get more info on the peace of code that would cause the problem.
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
Last Edit: 2015/03/24 13:21 By edwin2win.
The administrator has disabled public write access.
 
#12409
Re:Fatal error on slave sites 9 Years, 9 Months ago Karma: 0
Problem resolved! Purging in the back-end worked!

Thanks,

Emiel
joomblocks
Fresh Boarder
Posts: 8
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 1
get the latest posts directly to your desktop
2Win, Multisite(s) are trademarks of Edwin2Win.
Joomla