|
Aaron
|
September 13, 2021 at 5:57 pm
As the title says. Just moved my site and data to BlueHost for hosting services. When I activate the EE4 plugin, the screen goes all white and nothing more. Bluehost allows a secondary control panel to activate and deactivate plugins. When I deactivate, all comes back to a normal admin panel. I did download a fresh copy of the core plugin and upload it to ensure no files were missing.
Recommendations? Thanks in advance.
|
|
Aaron
|
September 13, 2021 at 6:11 pm
UPDATE: This message appears: ‘The requested EEW_Notes widget file could not be found or is not readable due to file permissions. Please ensure the following path is correct. [redacted] /plugins/event-espresso-core=reg/widgets/+notes/EEW_Notes.widget.php’ but this file does not seem to exist in the old or new files.
|
|
Tony
|
September 14, 2021 at 3:15 am
Hi there,
Your title is ‘Gravity forms plugin will not load’ so just confirm if it’s Event Espresso that doesn’t load when activated or Gravity forms won’t load when Event Espresso has been activated?
/plugins/event-espresso-core=reg/ is the = a typo here? I’m assuming so but just confirming.
With regards to the error: /widgets/+notes/EEW_Notes.widget.php
Event Espresso does not have a EEW_Notes.widget.php file or +notes directory by default but does dynamically load any directories in the root widgets directory and attempt to register widgets for them. That /+notes directory in widgets could be something from the migration to Bluehost and should be deleted (although its definitely not from ourselves, it’s still good practice to create a backup before you delete anything).
You mentioned you downloaded a fresh copy of Event Espresso and that is what I would recommend doing here, but may I ask how did you upload that to the site?
|
|
Aaron
|
September 14, 2021 at 9:17 am
I am trying to figure our what is cause and what is effect on this matter. Allow me to clarify more. 1) yes the path was a typo above. 2) When I activate EE plugin in the WP Admin panel, the screen goes blank, however, the url at https://www.utahccwcarry.com still loadings but with the error that will fade away after a moment. After it was mentioned the error regarding ‘_notes’ was nothing to do with EE, I went to Bluehost. She found this in the logs “14-Sep-2021 14:52:39 UTC] PHP Warning: implode(): Invalid arguments passed in /home3/utahccwc/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php on line 1139”. I deleted and re-uploaded from a fresh copy of EE. I looked at the line and it does not appear to be anything mind-blowing in code.
So, since this was a migration and of course, every hosting server has its own settings, I need to ask 1) is EE possibly not compatible with Bluehost? Does not seem likely but I should ask. 2) Is there anything that mind be on the DB side that could be causing this? It is the only element that has not been looked at. Next step is I am going to delete the /uploads/eventespresso files and see if that does something. Given that I have replaced the plugin files fresh, what other elements may be at play here?
|
|
Tony
|
September 14, 2021 at 9:32 am
1) yes the path was a typo above.
Ok, thank you.
2) When I activate EE plugin in the WP Admin panel, the screen goes blank…
Ok, so there is likely a fatal error being thrown, which ties into your other post.
After it was mentioned the error regarding ‘_notes’ was nothing to do with EE, I went to Bluehost.
?? Just to clarify here, I didn’t say the error isn’t anything to do with Event Espresso, that error will indeed be coming from Event Espresso. However, Event Espresso should not have a _notes or +notes directory within /widgets/ and the fact that there is one is what is causing the error.
I went to Bluehost. She found this in the logs “14-Sep-2021 14:52:39 UTC] PHP Warning: implode(): Invalid arguments passed in /home3/utahccwc/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php on line 1139”.
That line number is from out _require_file() method and again points to something weird going on with the directories.
I deleted and re-uploaded from a fresh copy of EE.
How did you do this? FTP/SFTP/File manager or via plugins menu in the dashboard?
1) is EE possibly not compatible with Bluehost? Does not seem likely but I should ask.
As far as I am aware, we’ve not had reports of incompatibilities.
2) Is there anything that mind be on the DB side that could be causing this? It is the only element that has not been looked at.
Possible, yes, there’s is a LOT going on within the database. However, if the database is migrated correctly is should be fine. The errors you are reporting don’t sound like database issues to me.
Next step is I am going to delete the /uploads/eventespresso files and see if that does something.
You can simply rename the directory to anything other than plain old espresso, so espresso-temp will stop anything from loading from those directories.
What do you have in there?
Given that I have replaced the plugin files fresh, what other elements may be at play here?
How did you replace those files?
Right now it looks like either a permissions issue or there are directories/files within the /plugins/event-espresso-core-reg/ directory that shouldn’t be there, EE is trying to autoload its classes, finding directories that shouldn’t be there and then trying to load classes that don’t exist within them.
|
|
Aaron
|
September 14, 2021 at 10:47 am
Thanks for the direction. I knew I was chasing some ghosts and couldn’t tell what was real and what was not. Your idea of how it is being upload (ftp) and permissions gave me the idea to delete all the plugins and use the WP Admin GUI.That seemed to resolve the issue. As I am sure you suspected, the ftp client must have either been chasing permissions somewhere or there was a ghost file hanging out somewhere. In the end, your thoughts were right on. Thanks for your help.
|
|
Tony
|
September 15, 2021 at 3:16 am
Great, I’m glad it’s working 🙂
I highly recommend not using FTP to update plugins and use the Admin GUI (which technically uses ftp in the background but just for the .zip as a whole), especially plugins as big as Event Espresso and there are a few reasons why but one is how easily those additional files/directories get transferred over.
I’ve seen various different file types and directories transferred during FTP that cause this issue (usually hidden . files or some hidden directory). As EE uses autoloading any rouge files or directories have the potential to cause issues as EE tries to automatically load files using our format, it can’t tell the difference between a ‘good’ directory and a ‘bad’ one.
Anyway, enough rambling from me, I’m glad you got it up and running and if you have any further issues just let us know.
|
