Solved Xenword-2017.10.26 activate error

[robru]

Warning: require_once(/var/www/html/wp-content/plugins/xenword-2017.10.26/src/admin/Multisite): failed to open stream: Success in /var/www/html/wp-content/plugins/xenword-2017.10.26/xenword.php on line 94

 

[ReneS]

Same here

Warning: require_once(/var/www/vhosts/hardwareinside.de/hw/wp-content/plugins/xenword-2017.10.26/src/admin/Multisite): failed to open stream: No such file or directory in /var/www/vhosts/hardwareinside.de/hw/wp-content/plugins/xenword-2017.10.26/xenword.php on line 94

Fatal error: require_once(): Failed opening required '/var/www/vhosts/hardwareinside.de/hw/wp-content/plugins/xenword-2017.10.26/src/admin/Multisite' (include_path='.:/opt/plesk/php/5.6/share/pear') in /var/www/vhosts/hardwareinside.de/hw/wp-content/plugins/xenword-2017.10.26/xenword.php on line 94

 

[LPH]

What? Grr.

I literally activated this dozens of times on different configurations. Adding a require_once shouldn’t be necessary. Composer should be autoloading.

Alright. I’m just waking up so I’ll grab the require_once statement and post in a bit.

 

[LPH]

I literally activated this dozens of times on different configurations.

Is this an issue of the Mac OS and case sensitivity?

Try this please. Go to /src and there are three directories named: admin, core, and includes. Please capitalize these to Admin, Core, and Includes.

Next, open xenword.php and place comments in front of 62, 65, and 94 which are all require_once statements. I'm guessing Linux distributions and case sensitivity are the issue with psr-4 barking loudly.

 

[LPH]

Is this an issue of the Mac OS and case sensitivity?

https://stackoverflow.com/questions/38730202/psr4-composer-autloading-namespaces

Therefore, renaming those three directories to being capitalized should do the trick. Comment out the three require_once lines.

 

[LPH]

Oh — and please let me know and I’ll zip up the changes tonight.

 

[LPH]

I've uploaded the zip anyway -- deciding others are reporting this issue -- and it should fix things. Let me know!

 

[robru]

I've uploaded the zip anyway -- deciding others are reporting this issue -- and it should fix things. Let me know!

When upload:

Fatal error: Cannot declare class XenWordPro, because the name is already in use in /var/www/html/wp-content/plugins/xenword-2017.10.27/xenword.php on line 37

When activate:

Warning: require(/Users/layneheiny/Documents/Sites/xenword4beta/community/src/XF.php): failed to open stream: No such file or directory in /var/www/html/wp-content/plugins/xenword-2017.10.27/src/Core/Connector.php on line 40

So far 2017.10.25 is the best version.

 

[LPH]

No way. Why is it trying to load my information? This is crazy.

OK. I'm at work and breaking a rule: internet use only for academic purposes. I'm going to have to step back and figure out what's happening and why it's trying to now pull my information.

Shaking my head

 

[LPH]

So far 2017.10.25 is the best version.

Which actually didn't work for the majority of people ... my lack of knowledge on how Composer works is starting to irritate me.

 

[robru]

No way. Why is it trying to load my information? This is crazy.

Get a rest.
At one point, you'll see where it's going wrong.

 

[LPH]

Please open /src/Core/Connector.php

Insert into the constructor:

$this->options = get_option('xenword_options');

The constructor will look like the following:

public function __construct() {
   $this->options = get_option('xenword_options');
}

Please let me know. If this fails then I'll try to rework the trait file.

 

[Gracie]

No way. Why is it trying to load my information? This is crazy.

It’s from the legacy code. The $fileDir is empty; therefore, loading your data. The code assumes an empty absolute path should be filled with your data.

Temporary Fix:
Go to database, wp_options, xenword_options
Add absolute path
Change use_xenword_legacy to 1 (for XF 1 installs)

 

[robru]

Please let me know. If this fails then I'll try to rework the trait file.

Sorry...

Fatal error: Cannot declare class XenWordPro, because the name is already in use in /var/www/html/wp-content/plugins/xenword-2017.10.27/xenword.php on line 37

 

[LPH]

Correct. I should have updated this thread. See my thread on notes for this version. The bridge options are an issue. I almost had it a half hour ago then tried from a blank site and user mapping was an issue. Upgrades appear fine. New sites are an issue.

I’m going to rest then try some other ideas.

 

[LPH]

This is the current state.

 

[LPH]

New version released.