greatmatter

The issue was that the meta_key needed a wpcf- in front. All good now.

We are experiencing the same issue.

We’ve discovered the source of the issue; I’d like to outline it here for posterity and just in case someone finds themselves in an edge case.

We have Google Cloud Armor implemented at the edge in front of our Load Balancer.

Removing/disabling Cloud Armor immediately resolved this issue.

We’re going to open a ticket with Google–but just in case anyone experiences this…try messing with Cloud Armor, or even your Web Application Firewall settings.

@dfactory My install is still missing three assets, like SVGs for the “previous” and “next” icons, etc:

/wp-content/plugins/responsive-lightbox/assets/img/loader.gif
/wp-content/plugins/responsive-lightbox/assets/img/icons.svg
/wp-content/plugins/responsive-lightbox/assets/img/icons.png

Yeah, we installed it–it doesn’t solve the problem.

Ok–figured out the issue.

In classes/replacer.php, getTargetFile() is not returning the correct path info for the destination in all cases. Sometimes, it’s returning:
/wp-content/uploads/[FILENAME]
rather than
[FULL PATH]/wp-content/uploads/[FILENAME]

As a result, it’s trying to move the file to a directory that:
1. Doesn’t/shouldn’t exist
2. Doesn’t/shouldn’t have permission to access
3. Isn’t web accessible

As a TEMPORARY and quick-and-dirty workaround, I added the following code at line 216:

// If the target file directory isn't QUITE right...
$upload_dir = wp_upload_dir()['path'];
if(substr($targetFile, 0, strlen($upload_dir)) != $upload_dir) {

  $targetFile = $upload_dir . '/' . pathinfo($targetFile)['basename'];
}

This fix will likely NOT work for others–but a fix is definitely necessary.

• This reply was modified 5 years, 4 months ago by greatmatter.

I did check the permissions, they are all set correctly. (Not to mention that regular uploads to the same folder work just fine)

Thanks, Alex–no, it’s still getting the same error message:
“The uploaded file could not be moved to /wp-content/uploads/[FILENAME]. This is most likely an issue with permissions, or upload failed.”

We’re getting the same error on the same line, but it doesn’t seem to be related to the folder–it’s just in /wp-content/uploads/

Permissions are all good, so we’re stumped.

A little clarification: the error is a 503 error. Any guidance is greatly appreciated.

We’re experiencing precisely the same issue.

Plugins Installed:
Contact Form 7
Contact Form 7 MailChimp Extension
Facebook Like Box
Google Analytics
Instagram Shortcode And Widget
Meta Box
Ninja Popups
Ninja Popups Themes Pack
Ninja Widget
PoliShortcodes
Postman SMTP
Recent Tweets Widget
Regenerate Thumbnails
Revolution Slider
Sidebar Generator
The Events Calendar
Total Donations
Ultimate Landing Page Free
W3 Total Cache
WooCommerce
WP Retina 2x
WPBakery Visual Composer

It’s hard to say at this point. My guess is that the non-admin user had requested a huge number of results to show per page (999). We did several things to make it acceptable:

• Threw more RAM at the server
• Enabled HHVM (for the record…holy smokes, this is fast)
• Enabled query caching
• Added an infinite scroll plugin to the backend

It’s now loading a lot faster for non-admin users. That said: when I monitored the queries, I noticed a WHERE clause that had an “ID IN ()” clause that had about 1,000 IDs. So I think a more appropriate title at this point is “Slow for users who want a lot of results per page”.

Ah, nevermind…the previous developer added some code that added the key in a theme:
$query->set( 'meta_key', 'vehicle_make' );

Sigh.

Believe it or not, you’ve helped tremendously. I wouldn’t have found this if you hadn’t mentioned the modifying queries. Thank you very much!

Or, even better, how do I remove if via the GUI? I don’t understand why it’s there in the first place.

I’d love a bit more guidance–should I add that as a hook, and if so, where? Obviously not the theme, but maybe a custom plugin?