kaldimar

@guermica1984 issue is coming from TheCartPress eCommerce plugin… did he edited such file by mistake? Probably deleting “Parameters” from line 14 (should be empty) would solve this…

@alain you got it right, in 4.1+ instead of $query->tax_query->queries being purely an array of arrays, it has one item of type string, in my case “AND”. Not a good design in my opinion. Type checking inside the foreach loop may be enough to prevent the notice being fired.

@tom it shouldn’t be related to PHP versions but rather in your previous server the error reporting was set to Off and in the new one all notices are exposed. If your site is live I’d suggest you to turn error reporting off for good measure.

FWIW, in line 87 the foreach is looping through an array which, for my home page, has four items, three of them arrays in turn and one (the second) is a string “AND”, this string is the one causing the warning.

A type check before evaluating the taxonomy index against ‘post_format’ may solve this?

Hi Chouby, I’m getting the same exact error:

Warning: Illegal string offset 'taxonomy' in /home/kaldimar/public_html/wp-content/plugins/polylang/frontend/frontend.php on line 88

In my case it only goes away by disabling the Cherry Plugin. Sadly, this is required for the theme to work, so disabling it is not an option and at the same time we’re relying on Polylang for internationalization. Please advise, thanks.

Now it works perfect without ghostscript enabled just by upgrading to 2.0.2. Thanks for taking your time to polish this plugin update!

The formats Imagick can process on my server do include PDF:

array(193) {
  [0]=>
  string(3) "3FR"
...
  string(3) "PDB"
  [111]=>
  string(3) "PDF"
  [112]=>
  string(4) "PDFA"
...
  [192]=>
  string(3) "YUV"
}

But on the settings page, just above the text field for the gs path, there is a notice saying

NOTE: exec() is not accessible. Ghostscript will not function.

This is a shared server and I can tell it’s rather limited. What do you recommend? Is my only option to rely on the Google service, or do I still have local alternatives?

Hello Dan, first, let me tell you I’ve been following this thread and trying your updates until this latest one, and I’m very happy to see this plugin evolve towards the best solution for document galleries across the WordPress ecosystem. Your prompt support and commitment to the improvement of your work is worth of our appreciation. Thanks!

Ok here is the translation https://wikisend.com/download/468970/SBCF-i18n-es_ES.zip

I’ve tested it on my site and everything looks fine in the settings page, and the submit button value is translated now. Feel free to peer-review it to be sure its worth your excellent plugin. Note that some translations are not strictly literal, but tuned to the specific context each phrase appears.

Hope this may be useful for other users. Keep the good work!

Sure, I can create a Spanish translation from your templates and send it back to you in case you may want to include it in an upcoming update.

Thanks for your answer. The string “Send email” is not in the WordPress translation file, and in the plugin folder I only have the German translation. Where can I download additional languages for this plugin?

Hi Dan! I apologize I was out of touch since last year, just downloaded the latest beta version and it worked fine out of the box! Perfectly created PNG thumbnails for the first page of PDF (only type I’ve tested so far). You’ve done a nice work here rewriting most of the plugin’s code but the results are worth! Thanks a lot for listening to the demands of the community, I’ll be looking forward to when this version is released as stable, in the meantime will try to keep an eye on this thread to help with further testing.

Regarding the size of the thumbnails, do you think the best way of controlling it would be by overwriting the styles for .document-icon img in a custom css file inside our theme? Or have you thought of using an attribute/option or some other way to specify a size that fits better with the active theme?

Its still happening on latest WordPress 3.8
I delved a little bit into the styles and found a css rule on /wp-content/plugins/wp-posts-filter/css/style.css line 9:

.metabox-holder {
    width: 85%;
}

If this rule is removed, the 2-column admin area goes back to normal. However I’m not sure if the rule is required for something else, just leaving my comment here in case its useful to debug from here.

Subscribing, I have the very same problem and its very annoying.

I can confirm that, I’m running WP 3.7.1, and after applying latest update to Ready-backup all /wp-admin/* pages are broken with message

Fatal error: Call to a member function getView() on a non-object in /home/website/public_html/wp-content/plugins/ready-backup/modules/adminmenu/views/adminmenu.php on line 24