Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Duplicate button not working
- This topic has 10 replies, 2 voices, and was last updated 7 years, 3 months ago by
rouge1.
-
AuthorPosts
-
February 27, 2019 at 1:18 am #21295
rouge1
ParticipantHi. It looks like the “duplicate filter” button isn’t working. That is all. 🙂
https://www.useloom.com/share/642e855ed0c34042b871e6ef467967ab
Is there another way to duplicate a filter?
Also, I’m working on this for a client on my development server. I’ll be adding this to their site, soon. Is there a way to export/import these filters? Also, I’m assuming the plugin can only be active on one site, at a time.
Thanks for a great product1
February 27, 2019 at 10:27 am #21298Ernest Marcinko
KeymasterHi!
Thank you very much for your kind words!
It was a known issue within the previous release. If you update to the latest one (4.14.6), and clear your browser cache, it should start working again. I couldn’t check your plugin version, as the site was password protected.
The license activation only affects the atuomatic updater, it does not affect nor limit the plugin functionality in any way. License-wise, test/staging/live servers for the same site are considered as ‘one’ end product, so you can have them installed with one on all three of them. The auto-updater should even recognize the ‘test.yoursite.com’ and ‘staging.yourseite.com’ and ‘yoursite.com’ type domains, so you can have the auto updater activated on all three. Otherwise, I usually recommend having the auto updater active on the live or staging site only. If you deploy from staging/test to live regularly, then activate it there, since the live is redundant.
I hope this helps!
February 27, 2019 at 2:14 pm #21305rouge1
ParticipantYou cannot access this content.
February 27, 2019 at 2:22 pm #21307Ernest Marcinko
KeymasterHi!
The plugin is not up to date, that is the problem, as I suspected. Once you update, the duplication will start working as it should 🙂
Yep, there is an export/import feature of course. I recommend updating all installations first to the latest release. Also, I do not recommend using this across separate WordPress installations, as term IDs, post IDs, user IDs etc.. are different for each installation. The filter/exclusion and other information that use this data will mismatch, or won’t work at all. The exceptions are test/live servers, where the live server is the exact copy (including database rows) of the test server.
February 27, 2019 at 2:29 pm #21309rouge1
ParticipantYou cannot access this content.
February 27, 2019 at 2:32 pm #21310Ernest Marcinko
KeymasterYou cannot access this content.
February 27, 2019 at 2:37 pm #21311rouge1
ParticipantYou cannot access this content.
February 27, 2019 at 2:51 pm #21312Ernest Marcinko
KeymasterYou cannot access this content.
February 27, 2019 at 3:09 pm #21314rouge1
ParticipantAm I able to control the IDS of the tags/categories? That goes beyond the name and slug, correct? As long as I’ve been building WP sites, I’ve never had to deal with tags, categories and such.
Thanks!
February 27, 2019 at 3:14 pm #21315Ernest Marcinko
KeymasterHi,
Unfortunately no, those are assigned by the database handler, those cannot be changed, and should not be changed. It’s basically a unique ID field to identify objects, which is an auto-incremental integer value in the database. That’s why the export/import only works on cases where the databases are also exported/imported via a deployment process.
February 27, 2019 at 3:18 pm #21316rouge1
ParticipantGot it! Thanks for all the help, quick replies, and the education! It’s all been very helpful. I appreciate it!
-
AuthorPosts
- You must be logged in to reply to this topic.