Forum Replies Created
-
Posts
-
No problem at all.
No need for another topic, this is fine 😉
You mean clicking the search box, then clicking away?
If so, then it’s a known issue. It’s already been fixed in the upcoming version, which should be available for download within a week 😉
It was because of an old compatibility code with internet explorer 7 – but it’s no longer needed.Hi!
You need to set up your permalink structure for wordpress to recognize the “/×¤×¨×¡×•× ×•×ª” url as the default search page. Currently your main url works, for example: http://www.persona.org.il/?s=test
The plugin is working correctly, it redirects to the correct page, but wordpress doesn’t know that it should be the search page.
I think you need some kind of modification to your .htaccess file, but I’m not sure.
I’ve found a tutorial that might be helpful: http://wpengineer.com/2258/change-the-search-url-of-wordpress/
Hi!
This sounds like a javascript issue. Try to switch the javascript source under the “Compatibility Options” submenu from Minified scoped to minified.
However if there is an error thrown from another javascript file coming from another plugin or theme, then this might not help.
If you check the javascript console (F12 on most browsers) when reloading your page, it might show something – an error or warning perhaps.
Okay. Then there are some safe update steps described in the documentation, first chapter, that should definitely help.
Hi!
I think it’s just a option inconsistency, because there is an option check on that line.
Try to deactivate and activate the plugin, then go to the caching options page from the ajax search pro sub menu and save the options without changing anything.
Sometimes transferring the database from one place to another causes options to be cached incorrectly.
Hi!
On the theme options you can change/upload your own icon for the magnifier, but if you want to change it as a whole I recommend doing it with CSS and leaving the HTML intact, because javascript actions are attached to that button and if you change the HTML structure the search won’t work anymore.
The search is purely ajax powered, thus you can’t “transfer” the result data from page to page. The redirect url is merged with the base site url. For example if you want to use the yourdomain.com/search/phrase/search+for+this url, then you only need to paste the url after your domain name, so in this case: search/phrase/{phrase} You don’t need to use the domain name, it is appended automatically.
No problem at all:)
I think everything will be ok now, there should be no bugs present anymore. You can feel safe.
Hi!
Yes. The problem was that the description length was 60 characters and the leftover stripped html tags were incomplete as I expected. Luckily this was not an error or a bug. All I did is changed the strip tags to this:
[code]<b>[/code]
So every other tag will be stripped besides “b”. The description should be visible now.
Well, that means it’s not the javascript either.
So it’s not the CSS because first of all there is not a single rule in the plugin CSS file that can apply to any other content than the plugin itself. Second of all it’s rendered the same way each and every page refresh.
But it’s not the javascript either, because no events are fired for at least 2 seconds and if I understand correctly the issue appears almost instantly, right after the page is loaded.
I’ve spent an hour refreshing the browsers on 2 machines like 500 times, but every single time the page is rendered correctly. I’ve tried lower, higher resolutions, clicking randomly, refreshing, interrupting the requests, but nothing at all.
I’m afraid that this is going to be something else. The fact that any computer in my location renders the page correctly at any given time, and for you is the opposite I suspect there is something wrong with the connection either on the server side or somewhere inbitween. What I mean is that either one or more of the CSS or javascript files doesn’t load, or loads incorrectly, or it’s a cache miss or something.
I honestly never encountered a strangest issue ever, and I honestly have no idea why the page is different for us.
Okay, I might see something.
You have category selectors activated. It’s not going to work on multisite, since each blog has different categories with different category id’s. So a category with the same name on one blog, might not exist on the other one, since they have different id’s. Unfortunately this is how WordPress works for now.
So by removing the category selectors (dragging them back and turning them off) should solve the issue.
Let me check that for you.
In the meantime, could you please provide temporary administrator and ftp access as well? It’s most likely impossible to tell if there is an issue by looking at the frontend.
Hi!
Indeed, they are extremely hard. I’ve tried to set up another virtual mashine with windows7 and tried these resolutions, but still no luck.
I’ve done some research in the meantime, and it turns out this is not going to be a direct CSS issue, since CSS is rendered the same way each and every time, so there is no way that some refreshes work, some not. Let’s rule out CSS as the direct cause for now. The next in line is javascript then.Since I’m still unable to replicate the issue, I have an idea which should solve this once and for all. I’m going to instruct you to make a modification to a certain file in the plugin. We are going to put a 2 second delay to the plugin slider loader script. This way, if this was a synchronization issue, then 2 seconds after the page load should be more than enough for any other script to do it’s things.
Open up the wp-content/plugins/related-posts-pro/includes/hooks.php file and right at the beginning at lines 11-36 you should see this code:
[code]<?php echo $scope; ?>(document).ready(function ($) {
$(‘div[id^="relatedpostspro_<?php echo $id; ?>_"]’).relatedpostspro({
"node": null,
"elements": ".rpp_item.rpp_visible",
"elementsAll": ".rpp_item",
"visibleClass": "rpp_visible",
"fadeoutClass": "rpp_fadeout",
"titleSelector": ".rpp_title",
"loadingSelector": ".rpp_cssloading_container",
"relevanceSelector": ".rpp_relevance",
"type": "<?php echo $options[‘layout_type’] ?>",
"isotopeLayout": "<?php echo $options[‘isotope_type’]; ?>",
"transitionAnimation": "<?php echo $options[‘transitioning_type’]; ?>",
"initialFilter": "post_type",
"autoplay": <?php echo ($options[‘autoplay’]==1?"true":"false"); ?>,
"autoplayTime": "<?php echo $options[‘autoplay_time’]; ?>",
"overrideFilter": <?php echo ($options[‘combine_filters’]==1?"true":"false"); ?>,
"minShow": <?php echo $options[‘items_count’]; ?>,
"defSortValue": "<?php echo $options[‘default_sorting’] ?>",
"defSortOrder": "<?php echo $options[‘default_sorting_order’] ?>",
"showSettings": <?php echo $options[‘show_options_visibility’] ?>,
"showSearchByDefault": <?php echo $options[‘show_search_filter’] ?>,
"exactSearchMatchOnly": <?php echo $options[‘search_exact_matches_only’] ?>,
"dots": true
});
});[/code]Now, we need to add a timeout to the inner function to wait after the document ready event fires. Change that code snippet to this:
[code]<?php echo $scope; ?>(document).ready(function ($) {
setTimeout(function(){
$(‘div[id^="relatedpostspro_<?php echo $id; ?>_"]’).relatedpostspro({
"node": null,
"elements": ".rpp_item.rpp_visible",
"elementsAll": ".rpp_item",
"visibleClass": "rpp_visible",
"fadeoutClass": "rpp_fadeout",
"titleSelector": ".rpp_title",
"loadingSelector": ".rpp_cssloading_container",
"relevanceSelector": ".rpp_relevance",
"type": "<?php echo $options[‘layout_type’] ?>",
"isotopeLayout": "<?php echo $options[‘isotope_type’]; ?>",
"transitionAnimation": "<?php echo $options[‘transitioning_type’]; ?>",
"initialFilter": "post_type",
"autoplay": <?php echo ($options[‘autoplay’]==1?"true":"false"); ?>,
"autoplayTime": "<?php echo $options[‘autoplay_time’]; ?>",
"overrideFilter": <?php echo ($options[‘combine_filters’]==1?"true":"false"); ?>,
"minShow": <?php echo $options[‘items_count’]; ?>,
"defSortValue": "<?php echo $options[‘default_sorting’] ?>",
"defSortOrder": "<?php echo $options[‘default_sorting_order’] ?>",
"showSettings": <?php echo $options[‘show_options_visibility’] ?>,
"showSearchByDefault": <?php echo $options[‘show_search_filter’] ?>,
"exactSearchMatchOnly": <?php echo $options[‘search_exact_matches_only’] ?>,
"dots": true
});
}, 2000);
});[/code]Hopefully I didn’t make any mistakes. The two snippets only differ in two lines.
After making the change make sure you clear every cache including browser and site. I’m expecting one of two possibilities after implementing this:
1. The problem goes away
2. The problem will appear after each page loadLet me know how it goes 😉
No problem at all.
I had to include the namespaced script versions as well mostly because of these types of conflicts. You don’t want to know how many times I have seen different jQuery versions manually included in site header AFTER the wp_head() call. The users were wondering why none of their jQuery plugins were working, and of course blamed this ‘stupid’ plugin and left a 1 star rating without asking.
Thank god this fix works more than 99% of the time.But probably the biggest and almost unfixable issue is the CSS conflicts because of themes. Let me show you a CSS rule from the Avada theme, which is the #1 best seller item on themeforest:
[html]#header-sticky .login-box .forgetmenot input,
#header .login-box .forgetmenot input,
#small-nav .login-box .forgetmenot input,
#side-header .login-box .forgetmenot input {
margin:0
}[/html]It looks harmless, but it’s this causes extremely huge issues. I’m not sure how familiar are you with CSS precedences, but an element targeted with an #id selector can’t be overridden by class selectors. So if the user puts the search shortcode within those elemenents, and in the search code I want to change the input margin I can’t do this:
[html]
.ajaxsearchpro input.proinput {
margin: 10px;
}
[/html]Because the theme rule will override this. The only possible solution if I use an #id for the ajax search pro. BUT, the plugin shortcode is re-usable, thus multiple instances MUST have different #ids, so how can I target those with a single CSS selector? I tell you how – impossible.
I’m not saying that theme is not good or anything, but WHY on earth does he use freakin IDs?? There is no reason to do that at all.
I had to work straight 2 days on a solution to introduce a new option for the upcoming search version: Adjustable CSS compatibility levels
It’s an extremely nasty dynamically-generated solution – basically it let’s the user to choose higher compatibilty level if something is not right on the frontend. The highest level generates lots of unneccessary CSS just to bypass the #id issue. It’s insane.I wish themeforest had higher standards at reviewing items, or provided some kind of guide to prevent these issues. It’s always the plugin developer to blame, never the theme developer.
I’m sorry for the long writeup, I hope it wasn’t too boring 😀
Anyways, if you need any more help or assistance, let me know!
The error is not acutally causes by that part, it’s this:
WordPress database error Got error ‘trailing backslash (\)’
[code](lower(dist_posts.post_content) REGEXP ‘paraprofessional|contract\\’)[/code]It’s either someone tried to search for a phrase with backslashes or attempting an SQL injection. the “\\” string might have been something else before processing. I would say it was not on purpose, doesn’t look like a injection pattern.
Anyways, it’s harmless because the wp database layer escapes and double checks everything and returns an error after terminating the query like this if something is not right, consequently the search returns no results.
Would you please check again? I cleared the search cache just to make sure, maybe that’s why you didn’t see the changes.
Phrase “church”, if I uncheck the “Religious Sites” filter, then no results ->OK
Result: http://i.imgur.com/07CpQC2.pngPhrase “church”, if I check the “Religious Sites” filter, then many results ->OK
Result: http://i.imgur.com/r2F1z61.pngPhrase “top panoramic”, if I check the every filter, then many results ->OK
Result: http://i.imgur.com/NIyXIT6.pngPhrase “top panoramic”, if I uncheck the “Museums” filter, then no museums in results ->OK
Result: http://i.imgur.com/QjbPxOq.pngPhrase “top panoramic”, if I uncheck the “Museums” and “Religious Sites” filter, then 2 results(Mamilla Mall, Acre Old Port) ->OK?
Result: http://i.imgur.com/vufG9eJ.pngCould you please double check if these are OK?
