Forum Replies Created
-
Posts
-
Hi!
I have moved your reply to a new ticket, it’s more convenient this way.
I checked the website and the problem is with the cloning. All of the ajaxsearchpro instances are using a unique id. The menu clones all of it’s contents including the search, so there are two elements with the same id’s on one page. Two elements with the same id’s on the same page cannot exist, it’s against the w3c standards.
Besides that the client side cloning faces another issue, that even if there was no ID on the search element, the initialization event was fired when the page was loaded, and that step cannot be repeated. (it’s the jQuery(document).ready(…))In other words it is impossible to put anything inside that mobile menu that is using javascript or any javascript library like jQuery as long as it clones the contents of another element.
A way to solve this is probably by editing the search id when it’s cloned (or after cloning), I’m not sure if it’s possible, and then make a new initialisation event for that new search instance.
I can take a look at that if you can send me temporary ftp/admin access, but I cannot promise that I can solve this (it might be impossible). Please open a new ticket with the login details and I will take a look at your site.
Hi!
Those are keywords suggested by a google service based on the search keyword. You can turn them off on the General options panel by disabling the “Keyword suggestions on no results” option: http://i.imgur.com/UqhipcU.png
Usually some words are treated by the database as “stop words” (or common words) when using Fulltext search mode. Most likely “type” is one of those words, so it’s ignored.
To quickly solve this issue I suggest to turn off the “Use fulltext search when possible” on the fulltext search settings panel: http://i.imgur.com/eVQCtmB.png
This wont affect the search speed unless you have a huge database.Don’t forget to turn off (if you have it on) or delete the cache after you change these settings. http://i.imgur.com/XXfJetc.png
I hope this helps!
Hi!
Thank you for the detailed information! I have found the bug in the search code and fixed it. It should work fine now!
Ok. I can’t see from the screenshot where is that coming from exactly. Can you make a wider screenshot and perhaps clicking on that error? I’m unable to reproduce this on any of my test installs.
On the other hand this is just a client side javascript error, it should not affect the statistics page (it’s not using the .sortable(), which causes the error), but I guess that the plots are not viewing because of this.
Also, if you cold provide temporary admin/ftp access it would help me a lot to locate the source of this as I can’t reproduce the issue unfortunately.
If you can edit the first post, then there are fields where you can add them. If not, then you can also create a .txt file or screenshot with the details and attach it to your post. (only me and you will see the file, other members don’t)
If it’s still not working, then I might need temporary admin/ftp access to do a quick debugging. Unfortunately I have no idea yet what is causing this.
Hi!
I suspect, that the search caching is activated. (at least I hope)
Try to open the cache settings and disable it, it’s most likely going to solve the problem: http://i.imgur.com/XPDciXo.pngAs I can tell from the screenshot you are using an outdated version of the search. Please upgrade to version 2.4, you can download it from codecanyon.
Steps to safe upgrade:- Remove all the search instances you have created
- Remove the shortcodes from all of the posts/pages and the widgets as well
- Uninstall the search plugin and delete the files
- Install the new version
This should solve the problem with the statistics page as well.
Hi!
Thank you for the login details! Once I logged in and clicked on the search settings the following javascript error came up in my dev tools:
Uncaught ReferenceError: tinyMCE is not defined shortcoder.js?ver=1.0.7:793
The file wp-content/themes/shp/core/backend/scripts/shortcoder.js had a fatal error on line 793 so I corrected it. It’s part of the current template (nVision). You should also notice the developer of the template about this issue – it was causing errors on other pages on your backend as well.
The following line was replaced:
if(tinyMCE.activeEditor){with:
if(typeof(tinyMCE)!= "undefined" && tinyMCE.activeEditor){Now the search should work without any problems.
Hi!
There is an option for that on the layout options panel: http://i.imgur.com/aiiS7d9.png
I hope that’s what you are looking for! 😀
Hi!
Please try the following things from the faq: http://wp-dreams.com/faqs/the-search-is-not-saving-the-changes-i-made/
It’s most likely a file/directory permission issue.You should also empty all caches (in case you are using any).
Hi!
Unfortunately it does not help much, but at least I know it’s a server side issue. There is a good chance that this error will disappear once you go to a live server from a local installation. If not, then I will gladly do a quick debugging on the search code if you can grant me temp access.
Let me know when you go live!
Hi!
Can you please provide url/temporary admin/temporary ftp access to the production site? I honestly don’t have any ideas what this could be. Most likely plugin/theme conflict of some kind, function redeclaraitions or something similar.
Hello!
May I ask you which version of the search were you running?
The versions before 2.0 were a lot slower then the current one. The plugin had been seriously reworked since then. Generally there are only a very few php files loaded, doing very few operations.
I’m attaching the newest version of the plugin to this post (this contains a few bugfixes which are not uploaded to codecanyon yet), hopefully you will get better results with the speedtest.
