chrisphilton

Found the issue:

$listlanguages = $this->model->get_languages_list(array('hide_empty' => true));

I don’t have any posts for my non-default languages, however I do in fact have translated content for them. I had the change choose-lang.php so I guess I won’t be able to automatically update.

Any reason for this empty check? Posts aren’t the only things that Polylang can be used to manage.

But why hash? You could instead use something like JSON? You wouldn’t need to make a new table, and you wouldn’t prevent scripts from systematically updating database instances of (unnecessarily) hard coded directories?

@photocrati – Honestly, I’ve been looking through lots of old support forums and many people have this exact same issue.

You keep saying in those threads, ‘resetting options should fix it’ and ‘migration’ is not a common scenario.

Many developers have ‘local’, ‘staging’, and ‘production’ environments that they regularly deploy between. I also think that it should be clear to you by now that using your external reset tool doesn’t decrypt hard coded Base64 post attachment settings (WHY WOULD YOU DO THAT?!?!?) and re-encrypt them in the database.

Do you understand the problem that we all have? If so, why do you keep responding as if you do not?

https://www.ads-software.com/support/topic/template-absolute-path-and-migration-to-other-hosting

@photocrati – I ran the reset tool to no avail. The reset option doesn’t effect individual instances of Attach to Post Display Settings.

The default display settings change just fine, but the Display Settings per post are hashed in wp_postmeta and do not change.

– Chris

I found display_settings hashed in postmeta.

1. Why would you hash anything for your plugin? Especially setting information that contains information that is environment specific and potentially needs to be systematically updated?

2. Is there a way to update all of the display_settings systematically when I go from local -> staging -> production?

Chris

Honestly, in the Attatch to Post pop dialogue… I can’t find any of the values stored anywhere in the DB or cache at all.

Are those stored on a 3rd party server? Or hashed in the DB somehow?

I have cleared all caches server side and client side, opened in a private window.

Just for more clarification, this is in regard to already existing posts that have galleries attached to them. The ‘attach new’ dialogue is fine. The already existing posts are what are showing the entire old server path as well as resulting in [Not a Valid Template].

Yes, some of the strings had <br> tags and a few <p> tags as well.

polylang_mo_10 post_content = the default registration title of the strings
polylang_mo_12 post_content = the pre-save error translated strings

Looks like after I hit save and get this error, polylang_mo_10 post_content is what starts getting used.

polylang_mo_10 in the DB is wrong
polylang_mo_12 is correct.

it keeps reverting to polylang_mo_10

Hey Chouby!

There is an awesome tutorial on git that GitHub has on there website:

https://try.github.io

Once you grasp the basics, it is really an amazing tool. A big advantage with GitHub is that you can do things like issue tracking and bugfixes, a wiki for how to use the plugin, manage contributions (with pull requests), and have discussions around certain pieces of code.

https://wptavern.com/wordpress-org-vs-github-for-hosting-wordpress-plugins-and-themes

https://sudarmuthu.com/blog/developing-wordpress-plugins-in-github/

https://thereforei.am/2011/04/21/git-to-svn-automated-wordpress-plugin-deployment/

Git is basically a branching system and as the repo’s owner, you can set it up to review / approve / deny contributions so that it isn’t a free for all.

You could even set up your documentation website to be base on git so that others can contribute to expanding and organizing the documentation your currently happen.

Let me know if you are interested and want any help setting this up.

Thanks again for making such an awesome plugin!