Re-publshing creates duplicates

Was it working before?

I never tried with this plugin; the WP/LR Sync has its own table in the database to remember the link between your Lightroom and WordPress and logically it should work in all cases (CDN for examples) but I am not sure what this plugin does.

If you disable this plugin (the Amazon S3 Cloudfront) and you check your Media Library, do you have images? Do you have unlinked files?

Your install should be full of unlinked files…

Sorry there is no before. I’m just exploring ways to set up a WP website (hopefully including your plugin!).

If I deactivate the Amazon S3 Cloudfront plugin, the media library data stays the same, but image links are broken (the browser placeholder is displayed in place of all images).
It seems upon deactivation the URL information for each media item changes from a link to S3 to a link into the local upload folder (which is empty).
No unlinked or duplicated images show up.

Some information I missed before (for completeness): WP is hosted in Heroku, Amazon S3 and CloudFront version 0.8.2, WP/LR Sync plugin Version 1.3.2 (WP) & 1.3.0.1300 (LR), LR version CC 2015 [1014445]

Can you invite the developer (Brad) to join here to debug the problem with us? For me it will be really hard since I don’t know the plugin at all and I don’t use Amazon S3, impossible to replicate the condition. And I am sure Brad had to face those issues many times, he will probably be able to help. FYI, we worked together two years ago to make our plugins work together (a different set of plugins) ??

I’ve opened a thread over there.

If there is any other way I can help (e.g., collect debug information or set up a testing environment), just let me know.

You can try it one more time, I did a rather big update on a few things, to avoid errors. Basically it’s a lot of checks and a safer way to write files (temporary ones).

Just updated the plugin and tried again. Same result.

After every re-publish a new media library entry is created and a new image file is saved to S3.

Okay maybe the problem is actually somewhere else in this setup. Just had a look at the database (using Adminium) and didn’t see a wp_lrsync table.

That seems to me like it might be a problem.
I’d expect this to fail slightly worse though, so I’ll have to double check this is actually what is going on.

Would this be a feasible explanation for the observed behavior?

There is a way you can reset the database (and it will create it if it’s not there). But you need to set the WP_DEBUG variable to true then you will have a new menu appearing in Tools called WP/LR Sync with many buttons. Choose “Reset”. This is normally for developers to use but you can try it.

This results in a SQL syntax error:

WordPress database error: [ERROR: syntax error at or near "(" LINE 2: id BIGINT(20) NOT NULL AUTO_INCREMENT, ^]
CREATE TABLE wp_lrsync ( id BIGINT(20) NOT NULL AUTO_INCREMENT, wp_id BIGINT(20) NULL, lr_id BIGINT(20) NULL, lr_file TINYTEXT NULL, lastsync DATETIME NULL, UNIQUE KEY id (id) )

Maybe relevant: The DB used is not MySQL but Postgres.

WordPress is not designed to be used with Postgres if I remember correctly. How does it work? Why are you using Postgres with WordPress by the way?

If you can modify the tables creation code to that it works for Postgres I guess that the plugin will work fine, but I am not 100% sure.

Heroku provides Postgres databases. The WP installation has been modified to work with PG4WP. (Sorry wasn’t aware of these specifics when setting out for this)

If this is only leading to this kind of problems, however, I’ll abandon this experiment and look for alternative, more compatible hosting.

Thanks for your spectacular support!

That seems a bit custom ?? Heroku is really nice, I have a few nodes apps running there. However, it is not a good place for a WordPress install I believe. Better to have a good old MySQL databases so that it can work with all the plugins you will want to try ??

I completely agree. But it was worth a try ??