Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Conflict with iThemes Exchange
This topic contains 1 reply, has 2 voices, and was last updated by Ernest Marcinko 8 years, 3 months ago.
- AuthorPosts
- September 2, 2015 at 1:55 pm #5765
Hi,
I’m building a website with iThemes Exchange as the e-commerce plugin. I installed Ajax Search Pro the other day and started having problems editing any page that contained an Exchange shortcode. This process caused a fatal error as shown here:“Fatal Error: Call to undefined function it_exchange() in /home/shopthecoconutro/public_html/wp-content/plugins/ithemes-exchange/lib/templates/messages.php on line 20
Description
The iThemes Exchange plugin code created an error that caused PHP execution to fail.
The code tried to run a function that doesn’t exist (it_exchange()). This type of error is typically caused by a simple typo (is_hom() rather than is_home()), by calling a function provided by a plugin when that plugin is not activated, by calling a function before it is ready (such as calling a function before the code that creates it has run), or by using a function that no longer exists (the function may have been removed from WordPress core or the plugin/theme that previously supplied it).
Solutions
Invalid code modifications can cause this problem. If you have made any modifications to the plugin, remove them and try to load the site again.
It is possible that this plugin’s code is out of date and that an upgrade is available. Check with the plugin’s author to see if an upgrade is available.
There may be a conflict with another plugin running on the site. Try upgrading the other plugins on the site. A plugin conflict can be ruled out by deactivating all the other active plugins on the site and checking to see if the error still occurs.
The iThemes Exchange plugin may not have been fully uploaded. Uploading the plugin again could fix the issue. Important: If you do this, you will lose any modifications made to the plugin.
Error Source Details
Type Plugin
Name iThemes Exchange
Version 1.22.0
Author iThemes
Path /home/shopthecoconutro/public_html/wp-content/plugins/ithemes-exchange
File lib/templates/messages.php
Other Software Details
WordPress Version 4.3
PHP Version 5.4.39
Full Error Details
Type Fatal Error (E_ERROR)
Message Call to undefined function it_exchange()
File /home/shopthecoconutro/public_html/wp-content/plugins/ithemes-exchange/lib/templates/messages.php
Line 20
Type Description This type of error indicates that PHP cannot continue to run the code. Typical causes of this type of error are code bugs that have typos, missing or incomplete files (such as a file that was only partially uploaded), and the code using more memory than it is allowed.
Note that this message is generated by iThemes.com products when an error is encountered on the site. While an iThemes product is generating this message, it is not necessarily the cause of the problem.”I disabled ASP and the problem goes away. The actual site works OK with both plugins running at the same time but there just appears to be an issue when editing pages that contain the shortcodes.
I have set “Run shortcodes found in post content” to OFF and “Strip shortcodes from post content” to ON but this hasn’t had any effect.
Do you have any suggestions on how I might be able to get around this issue?
JohnT
September 2, 2015 at 2:33 pm #5766Hi!
Since the error message does not contain information about ajax search pro files, I’m not able to tell what might cause this. As described it sounds like a missing file, but strangely it works when the plugin is disabled. The search plugin loads almost nothing on the editor pages to prevent any possible issues, so this might be somewhere in the initialization script.
I’ve installed the ithemes exchange free version on my test site, but I can’t find any shortcodes to test or use. I have to see or re-create the issue to suggest a solution, it can be literally anything. Do I have to enable a core add-on?
If you can provide temporary FTP and back-end access to your test server when I can debug the problem, that would be the best possible solution. I would probably find and fix the cause as well. I’m not sure if I can re-create this on my test environment.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
- AuthorPosts
You must be logged in to reply to this topic.