[Ernest Marcinko]

Hi!

The timthumb image url is giving me the following error:

A TimThumb error has occured

The following error(s) occured:
Could not create the index.html file - to fix this create an empty file named index.html file in the cache directory.

You can check it here: http://www.4g.co.uk/wp-content/plugins/related-posts-pro/includes/timthumb.php?ct=1&cc=FFFFFF&q=95&w=200&h=200&src=http%3A%2F%2Fwww.4g.co.uk%2Fwp-content%2Fuploads%2FLumia_930_4G_small.jpg

I suppose that timthumb needs an index.html file in the cache folder. Please try to create one with 777 permissions in the plugins/related-posts-pro/includes/cache/ folder.

[Ernest Marcinko]

Hi!

I thought you meant search autocomplete not the keyword suggestions. I have turned them off for you. The option is at “General Options -> Behaviour -> Keyword Suggestion on no Results?” if you need to turn it on any time.

[Ernest Marcinko]

Actually timthumb is a little bit more resource heavy, but there is not much of a difference – at least I couldn’t spot it. The non-timthumb version generates the images once, then loads them every time, so once an image is created it’s used all the time. Timthumb does almost the same but after the page load, so the rendering is delayed, but microrequests are made towards the server to check the cache. Anyways, the results are almost identical.

But if you want to use timthumb anyways, then check the permissions on the plugins/related-posts-pro/includes/cache folder. The permission should be 777. Some servers however does not tolerate this level so you can also try 766 then 755 as well. If none of them works, then the problem is elsewhere, or the permissions are locked via SSH.

Same thing for the plugins/related-posts-pro/cache/ (folder only) and plugins/related-posts-pro/css/ (folder and all of the contents!). After changing permissions on the css folder the error message should disappear after saving the settings regarding the “Error saving stylesheet…”.

If the error does not disappear then you can still try to turn off the inline styles option, it may still work. (there is a tiny chance the the server reports different permission values to the script than it really is, and it triggers the message)

[Ernest Marcinko]

Dear Thomas!

Can you please link me a page or post where the plugin is enabled? As I can’t see it anywhere I’m unable to tell where the problem might be. You can make a page and put the plugin shortcode inside of it so no other users will notice it, then just send me the url to that page.

Based on your description this sounds like a javascript issue, but I can’t tell until I see it. The error message indicates that the stylesheet could not be saved because the plugin has no permission to its own folders. That’s probably the reason why the timthumb isn’t working as well. Yet it should work with inline styles.

It is also possible that some other plugin is conflicting with the related posts pro, or there is a syntax error somewhere on the site – I really can’t tell.

You should also try to switch the script sources on the compatibility options panel from “Minified scoped” to “Minified”: http://i.imgur.com/ywfdD7B.png
I’m not sure if it will help, but it’s worth a try.

If you could also provide temporary administrator and ftp access it would help me a lot, as identifying the problem is only the first step, but finding the source and the solution is much harder. I would run a line-to-line debugging on the related posts code if neccessary. You can do this by editing your initial post in this thread and filling out the proper fields. (it won’t be visible to the public, just me and you)

[Ernest Marcinko]

Hi!

It’s working on my side. I tried the main page. For example I typed in “mariah”, it usually suggests “mariah carrey” but there are no suggestions. I also tried “iron” (for iron man), “food”, “drink”, but nothing. Are you sure it’s not working?

[Ernest Marcinko]

Hi!

It was a conflict with the image script so I switched back the settings to timthumb and it started working again. (on the cache options panel)

[Ernest Marcinko]

Hi!

It’s because I cant see the stylesheets loaded anywhere. Try to enable the force inline styles on the compatibility options panel. You can also try deleting the old search instance and creating new one and saving the settings again.

[Ernest Marcinko]

Hi!

I’ve looked at the backend of your site. I believe it’s because sabai is not using custom post types, but some kind of other method of storing the data. From what I can tell, the listings look like they are some type of pages or something similar. Same thing for the categories – those are not custom taxonomies, that’s why you can’t see them on the list.

I believe the creator had it’s reasons for not to using custom post types and custom taxonomies, however this way the content is not searchable by default. To make this work, it would require the major alteration of the search plugin, and if an update comes out to sebai, it would probably break it again.

I’m sorry, I would love to help you out, but in this case I’m unable.

[Ernest Marcinko]

Hi!

I made a quick fix on the search code. Please make a copy of the wp-content/plugins/ajax-search-pro/ folder to preserve the fix. It was only one missing character.

[Ernest Marcinko]

Hi!

1. It’s not possible with the advanced fields option, it only works with the custom fields. However you can do a quick hack to achieve this. Open up the plugins/ajax-search-pro/includes/search_content.class.php file and go to line 345. That should be an empty line. Put these lines there:

$_cats = get_the_category( $v->id );
if (isset($_cats[0]))
  $r->title = $_cats[0]->name.' - '.$r->title;

You should then see the first assigned category name to each post.

2. It’s because of preventing infinite loops in the javascript code. This would cause other issues in the plugins current state. I will try to implement something similar to the next version, but I can’t promise anything.

3. Not yet. The plugin uses a non-HTML5 placeholder for older mobile support, but it will get removed and replaced with a HTML5 placeholder in the next version, so this issue will disappear soon.

[Ernest Marcinko]

Hi!

The site is still full of notices on my side.

Notice: WOOCOMMERCE_USE_CSS is deprecated since version 2.1! Use Styles should be removed using wp_deregister_style or the woocommerce_enqueue_styles filter rather than the WOOCOMMERCE_USE_CSS constant. instead. in /var/www/quippe_2014/wp-includes/functions.php on line 3078

This is coming from woocommerce.

Notice: Undefined index: youtube_show in /var/www/quippe_2014/wp-content/themes/mercor/functions.php on line 512 Notice: Undefined index: twitter_show in /var/www/quippe_2014/wp-content/themes/mercor/functions.php on line 514 Notice: Undefined index: digg_show in /var/www/quippe_2014/wp-content/themes/mercor/functions.php on line 518

This is coming from the theme.

If you turn off the debug mode, then most likely these errors will disappear.

As for the search, something is creating invalid HTML tags and it breaks the rest of the site. Can you edit your first post and provide temporary ftp and administrator access, I can check that out for you and run a quick debugging.

[Ernest Marcinko]

Hi!

I’m getting the following errors on the page:

Notice: Undefined index: active in /var/www/quippe_2014/wp-content/plugins/wp-maintenance/wp-maintenance.php on line 405 Notice: Undefined index: disable in /var/www/quippe_2014/wp-content/plugins/wp-maintenance/wp-maintenance.php on line 424

It says, that it’s coming from the wp-maintenance plugin. You most likely have the debug mode enabled and the upper mentioned plugin is throwing the notices.

[Ernest Marcinko]

Hi!

Yes I did, sorry I forget to answer, I was a bit busy.

As much as I would love to help you, I can’t. Unfortunately I work alone as of now, and I have too many plugins and other sites (+customers) to take care of, so I don’t have any more time for other projects.

Sorry to turn you down on this one. If you want to stay somewhat compatible with the updates, then you should try to look at the code in the:

includes/search.class.php
and
includes/search_content.class.php

The search.class.php contains a class which is the parent of ‘other’ search classes. (like the content serach). So if you examine the the search.class.php (wpdreams_search) and search_content.class.php (wpdreams_searchContent) you will see that the wpdreams_searchContent class is derived from the wpdreams_search class. It was supposed to be abstract, but it’s not, mainly because of php compatibility and other issues.

So if you create a new class derived from the wpdreams_search class then there is a very good chance that your code will be almost fully compatible with the new updates, because the wpdreams_search class will not change for sure, and your code would be only an addition to the current search code. You can use the wpdreams_searchContent class as a sample to create your own.

Best of luck, and sorry again that I can’t participate in your project!

[Ernest Marcinko]

Hi!

I’ve applied a fix on the code, I’ve tried it for a few characters like: В в Б б
it was working for me, but I’m not sure as I don’t speak russian. Please try it now, I hope it fixed it.

[Ernest Marcinko]

You don’t need to worry about that. The updates always cover the fixes I make.

[Author]

Posts