Tell us what you are trying to do?
I am trying to edit pages on my staging site. We're having trouble with the toolset forms not showing in the front end, and now I cannot edit any pages with toolset items on them. I have disabled/deleted the most recent plugins I've added with no change - though I was able to edit and update the site with no problem when these were enabled.
Some pages open up but the update button is inactive , and some pages are blank. Pages with not toolset items open and edit with no error.
A user who was testing the site for me got an internal server error message when trying to submit a form, but another test user submitted their data with no problem. I'm at my wit's end.
We were hoping to go live with this site by the end of the month, so I need to get this resolved as soon as possible.
What is the link to your site? geag.dreamhosters.com
Hello. Thank you for contacting the Toolset support.
We will require more details about where you added your form as well as admin access details and steps to reproduce the issue and what data we should use to see the issue.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Can you please be specific with what post or forms or views you have issue with. Can you please share problem URL so I can see what is going wrong with your setup.
Also, a user who is helping me test the site sent me the image below when she hit submit on the member directory form. All her images saved in the media library thought
PHP 8.1 is currently not supported due to some issues. We’re working on fixing this. In the meantime, please use PHP 8.0 version.
While Toolset works with PHP 5.6+ and MySQL 5.6+, they reached the official End Of Life, and are not recommended for security and performance reasons.
Can you please downgrade the PHP version to PHP 8.0.x and try to resolve your issue.
what is the difference between 8.0 and 8.0 FastCGI?
Everything starting working after downgrading to 8.0 FastCGI except for the editing the pages that opened as a white screen and the one that had an inactive update button. I recreated the contact page and member directory and can now edit with no problem. I can still downgrade to plain 8.0 if you think it's best. I'm struggling with site speed so I want to make sure I make the best choices possible.
What do you recommend?
Here you can find the difference between normal PHP 8 and PHP 8 with FastCGI: hidden link
I do not see any other user reported such issue but if it does not work with normal PHP 8.0.x then I will require duplicator copy of your site to debug the issue further.
No difference in function when I downgraded to regular 8.0. However, now that I can edit again, whenever I try to add an image to a page with a toolset component, there's an issue with the media library. I'm attaching a screenshot of the issue.
I'm getting so frustrated! I know most of it has to do with me needing to educate myself more on web dev: I do appreciate all your help.
If we are in different timezone and you will require help in your timezone, please let me know and I'll transfer the ticket to support person who work closely in your timezone.
I'm totally not frustrated with you! Just aggravated with the situation and with myself for not grasping more of this. I appreciate your assistance. I'm happy to keep working with you or if it's better, you can shift the support person.
Hopefully here are the duplicator files you need: hidden link
Regarding the image issue - I have no problem adding images when there is no toolset component on the page. Dynamic images for things like views work fine. Just accessing the media manager. I disabled all plugins that have been installed since the problem began (and some others) and had no change in the situation. I can work around it for now -- we need to get this site moved over to the main domain by the end of next week. Hopefully we can figure out the issue. Everything seems to be functioning correctly on the front end.
