Forum Replies Created
-
AuthorPosts
-
Ernest Marcinko
KeymasterHi!
Sorry for the late response, I recieved a peak amount of requests, I just got to you.
I have found the problem, it was indeed an issue with the plugin. I have fixed it on your server and I’m going to implement it to the next release as well so it won’t happen again.
I’ve also found a problem with the height of the elements, so I have added the following custom CSS code to fix it:
[html].horizontal .resdrg .item {
height: auto !important;
}[/html]The results only allowed static height, but then the description was cut off for some items. This code allows to stretch to the highest item height without cutting off the rest of the description.
Ernest Marcinko
KeymasterActually, yes, and it’s probably better that way. Try changing the whole thing to this:
[php]add_filter( ‘rpp_item_after_postprocessing’, ‘rpp_add_category_titles’, 1, 1 );
function rpp_add_category_titles( $post ) {
// Get the post categories
$post_categories = wp_get_post_categories( $post->id );
$cats = array();// Concatenate category names to the $cats variable
foreach($post_categories as $c){
$cat = get_category( $c );
$cats[] = $cat->name;
}if ( count($cats) )
$post->author = implode(", ", $cats);return $post;
}[/php]Ernest Marcinko
KeymasterIndeed, I tested it and there was an error. Change line:
[php]$post_categories = wp_get_post_categories( $post->ID );[/php]
to
[php]$post_categories = wp_get_post_categories( $post->id );[/php]
and it should start working 🙂
Ernest Marcinko
KeymasterHi!
I think a better solution would be to use a filtering function, so the source code is not changed and it’s update proof.
I’ve put together a function that might do the trick. Put this to the functions.php file in your active theme directory:
[php]add_filter( ‘rpp_item_after_postprocessing’, ‘rpp_add_category_titles’, 1, 1 );
function rpp_add_category_titles( $post ) {
// Get the post categories
$post_categories = wp_get_post_categories( $post->ID );
$cats = "";// Concatenate category names to the $cats variable
foreach($post_categories as $c){
$cat = get_category( $c );
$cats .= " ".$cat->name;
}if ( $cats != "")
$post->author = $cats;return $post;
}[/php]Make sure to save the related posts pro options to clear the posts cache.
I haven’t tried this code, but I’m hoping it will work.
December 28, 2015 at 12:16 pm in reply to: Null Custom Field Dropdown Value / Broken Exclude Taxonomy #7160Ernest Marcinko
KeymasterHi!
1. I’m close to releasing an update, but I think first I will investigate if there is any way I can implement a bypass for null values. I know I tested a few possible solutions before, but those were absolutely killing the overall performance, maybe I can find something better this time.
2. I have found the problem. The function checking the term ids within the exclusions array was defined incorrectly. I’ve fixed it and putting it to the upcoming version of course. It’s a minor bug, nothing serious 🙂
Ernest Marcinko
KeymasterI’m not sure what should I look for on the screenshot. Is the text missing or something else?
Is there an example where I can look at this?
December 22, 2015 at 1:00 am in reply to: Null Custom Field Dropdown Value / Broken Exclude Taxonomy #7145Ernest Marcinko
KeymasterHi!
1. Well, if you want to filter a single numeric value (I’m guessing year?), then as a possible solution might be to not use the “EQUALS” operator, but rather “LESS THAN” and have a bigger number as the default value, like so:
[code]3000||All years**
2017||2016 and before
2016||2015 and before[/code]and so on..
In the first case each record, no matter which year is less than 3000 so the result set is not reduced. For the other ones, the year must be bigger by 1, as the “less than” operator is not inclusive.
The downside of this solution is that it does not filter by an exact year.Another possible solution is to use a <span class=”code”>Range Slider</span> type, and have the low – high values at the lowest and highest date.
I’m working on a solution to accept unset/null values, but it needs lots of testing, as the current solution has a great performance and I do not want to give up that under any circumstances 🙂
2. The configuration looks all right, there is definitely a bug somewhere. Can you also give me temporary FTP access to the development environment? I would like to debug the search code to find why is that happening. Weirdly it works with the categories, but not the taxonomy terms.
December 21, 2015 at 11:09 am in reply to: Null Custom Field Dropdown Value / Broken Exclude Taxonomy #7132Ernest Marcinko
KeymasterHi!
1. NULL values won’t work (meaning the custom field is not defined for the post) due to an optimization. A possible workaround is to have at least a “space” character as the value for the custom field, and have something like this as the first selection:
||None
2. I might need back-end and FTP details to check on this one. I’m not able to re-create the issue on my test environment.
To safely add the details you can edit your initial post in this thread, or upload a .txt file attachment. Both methods are safe and visible to only me and you.
Ernest Marcinko
KeymasterHi!
1. It works on the back-end, so it’s definitely an aggressive override causing it. I cannot locate which one, but I have a solution 🙂
Place the following script to the footer.php of you active theme just before the closing body tag: http://pastebin.com/raw/VzmiUDVKIt’s basically a a mildly modified version of the script that handles the clicking on the “try these” keywords. It directly connects to the “try these” links, removing other handlers.
2. Your configuration seems to be correct, so it’s definitely a bug. Can you please provide temporary FTP as well? I will have to do some debugging on the plugin files to find where the issue is.
Ernest Marcinko
KeymasterHi!
The first issue might be related to stripping HTML tags incorrectly. On the Advanced Options -> Content panel, remove everything from the HTML Tags exclude from stripping content option: http://i.imgur.com/uDOt16v.png
That way it will strip every HTML tag from the results, and no unclosed tag issues should appear.
The second issue is definitely not because of the exact matches. I’m guessing maybe a configuration issue on the index table, but I’m not sure. I cannot see login details on the ticket. Can you please add them, and I will check the configuration on the back-end.
Ernest Marcinko
KeymasterHi!
The biggest problem is that the Android browser is not a single browser, but it’s vendor released, and seems like every old device has a different one. I have found a Virtual Machine image with android 4.2 pre-installed with the Android Browser, but everything is working for me with this one.
It’s probably a vendor/device or specific version related issue, I’m not sure how I’m going to debug this. At least mobile chrome is same on all devices…
Ernest Marcinko
KeymasterHi!
The look of the default results page is indeed printed from the search.php in your theme directory. It’s true for the most themes, some others might use different files.
If you decide to customize that page, I recommend creating a child theme, so you won’t loose your modifications on updates.
Unfortunately I cannot provide an exact tutorial on how to customize that file, as it’s very different for each and every theme out there. If you are unsure of some things, I highly recommend asking the theme author for advice about modifications. They usually tend to be very helpful.Ernest Marcinko
KeymasterYou are welcome! Let me know if you need any help.
If you like the plugin, you can leave a rating on it on your codecanyon downloads page, it’s greatly appreciated.
Happy holydays!
Ernest Marcinko
KeymasterHi!
Thank you for the details, it made my work much faster 🙂
I’ve actually found a possible bug in the plugin, and corrected it in the code. The plugin should not be visible anymore on the archive pages 🙂
December 17, 2015 at 9:51 am in reply to: website shifts position when using exsisting search field #7112Ernest Marcinko
KeymasterHi!
Yes, that CSS looks correct to me.
To fix that problem, you will have to open the header file where you put the search shortcode in.
The faulty code should look something like:[html]<div id="search-box">
<div id="search-box">
…. some code is probably in here….
</div>
</div>[/html]and it should look something like:
[html]<div id="search-box">
…. some code is probably in here….
</div>[/html] -
AuthorPosts