This topic contains 8 replies, has 2 voices, and was last updated by 
- Posts
Hi, my goal is to deploy db changes automatically between staging and production environment.
I see that the plugin uses the following tables:
ajaxsearchpro
ajaxsearchpro_priorities
ajaxsearchpro_statistics
asp_index
Can you please elaborate on
1) tables may be ignored. Production and Staging DBs may use them independently
2) tables which should be uploaded.
Are there any tables that plugin uses which i missed? (posts, posts_meta, etc…)
Thanks in advance.Hi!
The
– {prefix}_ajaxsearchpro
– {prefix}_asp_index
..tables are the most important, as the first one contains the search instance configurations, the second is the keyword index (if used). The statistics and the priorities are not crucial.There are also options set in the {prefix}_options talbe, each is prefixed with ‘asp_’ so it’s easier to find them even manually. I highly recommend syncing those as well. Those contain the options from the compatibility, performance, statistics etc.. submenus. If not synced, the defaults are used automatically.
It is also possible that there is post meta set under the ‘_asp_metadata’ and ‘_asp_additional_tags’ keys in the post_meta table. However, if you don’t use the ajax search pro meta box options on the post editor screen, these can be completely ignored as well.
I hope this helps!
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
Hi, Ernest,
Thanks a lot for a detailed and fast response.
Just to confirm i got u right.
If ajax search pro plugin is configured in dev/staging environment and these configurations need to be deployed to production environment.
tables
– {prefix}_ajaxsearchpro
– {prefix}_asp_index
data in {prefix}_options table prefixed with ‘asp_’
and possibly meta data in
_asp_metadata
‘_asp_additional_tags’
-{prefxi}_post_meta table
should be deployed.
Modifications in
ajaxsearchpro_priorities
ajaxsearchpro_statistics
pertain to a running system (production)
so no need to deploy them?-
This reply was modified 6 years, 2 months ago by
Hi,
Yes, that sounds correct to me.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
Hi, Ernest.
My goal is to generated diff script for deploying changes between staging/production environments, so that only needed changes will be deployed.
Was wondering if changes to db can be detected with sql compare tools like Toad for MySQL?
Made a little test:
1) Tried to change the setting as in GetImage.png
2) Exported tables of the plugin:
{prefix}_ajaxsearchpro etc..
with sql dump.
before and after change.
3) Imported the dumps to different local dbs
4) compared them with Toad and couldn’t find the difference.Or alternatively, there’s need to import the dump as is?
Thanks in advance.Hi!
I believe there is only like 2 options within the instances that may be specific to an installation, and those are custom magnifier and settings icon uploads. But if you don’t use them, I assume you can just simply import the dump as it is, it should make no difference.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
Hi,
Thanks.
Actually, the setting in question was Advanced Title Filed. In staging it worked, in production did not until importing the dump as is.
As i said, diffing with Toad couldn’t detect any difference.Hi!
That is indeed strange. I’ve quickly examined the code that is responsible for displaying that field, but I could not find anything that would affect it. I’m not sure why is it happening to be honest.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
Np.
Thanks a lot. Will try again and let u know.
Maybe i missed smth.
Regards-
This reply was modified 6 years, 2 months ago by
You must be logged in to reply to this topic.