Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Problems with the Ajax Search Pro plugin
This topic contains 15 replies, has 2 voices, and was last updated by Ernest Marcinko 1 year, 3 months ago.
- AuthorPosts
- December 17, 2021 at 3:43 pm #35999
Hello,
I had to disable all plugins to identify a specific issue with the operation of the site. When I tried to reactivate the Ajax Search Pro plugin, I was pleasantly surprised to find that the site no longer works (see the attached screenscreen).
Can you help me fix this?
I mention that the theme used is AVADA, version 7.6Thanks
Attachments:
You must be logged in to view attached files.December 20, 2021 at 10:49 am #36006Hi,
It looks like as if a file corruption issue, and the plugin data is printed into the header.
The best possible solution to this is to try to completely remove the plugin and reinstall it again, to make sure all the files and the database are completely in tact:
1. Make sure to delete the plugin completely – this is very important.
2. Then, download the latest version via codecanyon dashboard and install it via the plugin manager.
3. Try activating the plugin, even if some errors pop-up, navigate to the maintenance page and do a full plugin wipe: https://documentation.ajaxsearchpro.com/installation-instructions/uninstallation-and-reset#complete-uninstallation-including-all-plugin-data-wipe
4. Delete the plugin again via the plugin manager.
5. Install and activate again – now no error messages should show up whatsoever.This should completely clear all possible integrity issues.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
December 20, 2021 at 11:29 am #36007Hi,
Unfortunately, I can’t execute step no. 3 and following because the site becomes inaccessible after activating the plugin. What can I do to resolve this issue?
Thanks
December 20, 2021 at 1:12 pm #36010If you want, you can add temporary FTP and back-end access, and I can try to check what the cause is or where is the error thrown exactly.
Best,
If this is not a file or database issue, then something else is conflicting. The plugin on it’s own should not cause any errors on activation whatsoever.
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
December 20, 2021 at 2:03 pm #36013You cannot access this content.December 21, 2021 at 1:09 pm #36020You cannot access this content. Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
December 21, 2021 at 2:12 pm #36026You cannot access this content.December 22, 2021 at 2:47 pm #36051Thank you!
I have cleared the memory, now it should be fine without any error messages. It was some sort of a database inconsistency error, I don’t know what exactly caused it, but it is clear now. It should not happen again, it is very unlikely, it was probably something random.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
December 22, 2021 at 2:52 pm #36052I’ll try again later to see if there is another error and I’ll come back with an answer
Thank you very much!
December 22, 2021 at 4:14 pm #36058It works!
Thank you very much for your help!
Regards,
DanDecember 22, 2021 at 9:16 pm #36060Pff !!! I deactivated / reactivated the plugin and the error reappeared !!!
December 23, 2021 at 10:51 am #36071Please use the attached version if you want to reinstall the plugin. I may have indentified a possible cause, I think we can remove that line and resolve this issue once and for all. I have installed in on your back-end, and it seems to be all right now.
The upcoming release should be okay, if this work, then I will make the changes permanent.
Best,Attachments:
You must be logged in to view attached files.
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
December 23, 2021 at 11:10 am #36074I can’t download the attachment. How can I do that?
December 23, 2021 at 11:49 am #36079Done, I managed to download it
December 23, 2021 at 11:53 am #36080It seems to work with the version you installed in the back-end.
I hope there are no more errors along the way.Thanks,
Dan - AuthorPosts
You must be logged in to reply to this topic.