Forums › Forums › Search & Filter Pro › Search Forms Options Not Saving after duplicating site to Staging Environment
- This topic has 5 replies, 2 voices, and was last updated 9 years ago by
Trevor.
-
Anonymous(Private) March 15, 2017 at 7:15 pm #97128
Hello,
So I S&F working perfectly on a production site I built. However, now my client wants me to make their site multi-lingual. So I copied the site over to a directory in the root of the production site WordPress install and setup a sub-domain.
I’ve done all the normal steps to have the site use the staging sub-domain, and everything else on the site is working as expected.
However, with the S&F forms, I noticed how only the search form displays, the results no longer display and are giving me the “Notice: This Search Form has not been configured to use a shortcode” message.
However, now when I go to the forms Settings and Defaults it no longer has my original options selected (the type of posts to search, the display method, …etc). I know the settings I need, but it just won’t let me save now. Anytime I make a setting change, and hit update, it reverts it back to what I’m guessing are the default settings.
Just to give you a little more info. The configuration settings and limits in the user.ini file are set high enough that the limits should not be an issue.
I have a custom template for each of the search form results I have via a php file named using the ID of the form, and is in a directory called /search-filter/ in my theme root. The template I’m displaying these in are using the shortcodes, with the correct form ID’s for both the form and results.
I’ve tried deactivating all other plugins and switched the theme to the Twenty Sixteen theme, and still does not let me save any options in the form settings.
So like I said, I have all this working on the production site, and it will let me save new settings. The only things different about the copy in the staging environment are:
- URL (sub-domain of production domain)
- Install locations – in a folder in the root of the production WP install
- The addition of WPML plugin and couple add-ons (even though I deactivated while trying to troubleshoot)
Any advice/help would be greatly appreciated.
Thanks
Trevor(Private) March 15, 2017 at 8:04 pm #97162It would rather depend how you migrated the site over I suspect. It sounds like part of the database was not moved or copied.
To test this, try making a new test form and save that. Did that work?
Migrating a WordPress install is a complex process. I never to it manually. Instead I use tools like Duplicator.
Anonymous(Private) March 16, 2017 at 1:44 pm #97274Hi Trevor,
Thanks for the speedy reply. I did what you suggested, and creating a new form does allow me to save options.
So does that mean that part of the DB didn’t get copied over? My client’s IT guy is the one who setup the staging area for me, so can’t say exactly how he did it.
Would you know if there is a way I can copy over just the part of the DB I need, or at least everything related to S&F, or would I have wipe everything and start over? I’m really hoping I wouldn’t have to because I’ve already spent a good amount of time working on the translations part.
Trevor(Private) March 16, 2017 at 2:03 pm #97289Given where you are at now, my best/quickest suggestion would be to recreate the forms and modify the shortcodes or ID usage. And for the future think about how you migrate a site.
For myself, I use a host that gives you staging sites that, pretty much at the flick of a switch, becomes the real domain/site, or can be cloned to another of their servers without such issues. That option may be possible with your hosting. Worth investigating.
Anonymous(Private) March 16, 2017 at 2:08 pm #97293Thanks for your help, Trevor. Unfortunately, the web host is based out of Europe and their IT person is the only person allowed to access. I was only provided FTP, and when I originally built the site locally, I had to send him the exported sql file. But you’re advice is appreciated and will keep that mind when for future reference.
Thanks,
Ryan
-
AuthorPosts