[Resolved] My site keeps going down every time I install the Toolset Views plugin.

[Author]

Posts

[Dee_DeeA2948]

I am trying to: Utilize the types plugin

Link to a page where the issue can be seen:
I uninstalled the plugin so that the side would go back up. I've provided an error log below.

I expected to see: A working site

Instead, I got: This error: This page isn’t working box####.temp.domains is currently unable to handle this request.
HTTP ERROR 500

Error Log: (hundreds of lines of the same thing repeating)
[15-Jan-2019 05:27:59 UTC] PHP Warning: Illegal string offset 'height' in /home4/prepnavi/public_html/wp-includes/media.php on line 989
[15-Jan-2019 05:28:46 UTC] PHP Warning: Illegal string offset 'width' in /home4/prepnavi/public_html/wp-includes/media.php on line 988
[15-Jan-2019 05:28:46 UTC] PHP Warning: Illegal string offset 'height' in /home4/prepnavi/public_html/wp-includes/media.php on line 989

[Nigel]

Hi there

The PHP warnings look like they are related to an issue with SVGs, maybe when used in widgets (this is not necessarily related to Toolset).

However, PHP warnings shouldn't produce 500 errors, which points to a fatal syntax error that you possibly missed because your log is full of so many PHP warnings.

To try and isolate the problem(s), I would first test with a minimal install.

So, switch to a default theme (e.g. twentynineteen), and disable all plugins.

Now delete (or rename) your debug.log so that you can start with a clean one and more easily see the errors and/or warnings.

Activate Toolset Types and Views.

Does that work?

Any errors in the PHP log?

Now re-activate other plugins one-by-one and keep checking for anything breaking or messages in your logs, until a problem arises. Make a note of what you just did, as well as what is reported in the logs, and share that with me.

If you get as far as re-activating all plugins without problem, switch to your chosen theme and see if that produces any errors.

[Dee_DeeA2948]

The PHP warnings look like they are related to an issue with SVGs, maybe when used in widgets (this is not necessarily related to Toolset).
***Should I remove the SVG widgets?***

However, PHP warnings shouldn't produce 500 errors, which points to a fatal syntax error that you possibly missed because your log is full of so many PHP warnings.

To try and isolate the problem(s), I would first test with a minimal install.

So, switch to a default theme (e.g. twentynineteen), and disable all plugins.
***By switching to a default theme and disabling plugins, will I lose the work that I've created? For example, when I switch to another theme, temporarily-- and switch back to the desired theme, will the styling get ruined? I've had issues with changing Astra themes in the passed, so I'm very hesitant. Also, I've created items in the plugins, views, custom post types, etc. Will I lose this?***

Now delete (or rename) your debug.log so that you can start with a clean one and more easily see the errors and/or warnings.
This should be easy.

Activate Toolset Types and Views.

Does that work?

Any errors in the PHP log?

Now re-activate other plugins one-by-one and keep checking for anything breaking or messages in your logs, until a problem arises. Make a note of what you just did, as well as what is reported in the logs, and share that with me.
***I did this from Bluehost. When the site went down we deactivated each plugin, 1-by-1 until we determined that the views plugin was causing the issue. Is there a way I can just remove the views plugin and start over?***

If you get as far as re-activating all plugins without problem, switch to your chosen theme and see if that produces any errors.

[Dee_DeeA2948]

My issue is resolved now. Thank you! I looked at the debug log and noticed something about memory. I was messing around with the "views" pluggin, making a ton of changes to learn how it all works and I think I reached some kind of memory capacity within a certain time period. This morning I re-installed the plugin (not going through any troubleshooting steps) and BAM! It worked as it should. Phew! I do appreciate your help. If this ever happens, I will refer to your troubleshooting steps.