Happy Monday!
So I’ve been noticing that gform_column_input has has been throwing errors:
When I try to implement it into forms, it starts off fine, and my list field has a working checkbox or other feature. On submit and usually starting with the third row, it pushes the content of form fields to the cell on the left.
I do need to update. I’m waiting for the weekend to shutdown the site, backup and do updates.
The debugging plugin just does the same thing as turning plugins off and on again, so it seems unnecessary. In any case, I think last time i tried it and it threw its own error on my site.
My theme might have issues, but I’m too deep in (done a lot of customizations) to change my theme now. So I generally feel it is better to find the conflict within the Theme and work around it… or just work around it from the beginning
Yes, the Debug add-on is the same as deactivating your plugins and activating an Automattic Twenty * theme. It just allows you to do that without affecting any site visitors, if that is an issue for you.
It won’t work on multisite. However, if it throws an error, I recommend opening a support ticket for that.
I just cloned one of my sites to change a few things without having an impact on visitors and wanted to change the theme too. Got the ‘theme is activated’ message, but the theme just didn’t change. After about 10 tries and disabling plugins etc. I realised the mu-plugin file for having a different theme active in the Dashboard was cloned too ofcourse…
So, long story short: don’t forget you have this active when you’re trying to change themes