-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not seeing frontend translation dialog #3
Comments
Hi Ofer, Don't know how I solved it on this other site so any insight would be helpful! |
Hi, I am sorry it took me so long to answer your issue here. I assume that you used your own widget, so the ticking checkbox was not available, the trick is to simply add the parameter "tpedit=1" to the end of whatever url you want to enable editing for, assuming you are logged in as a user with sufficient translation permissions, Good luck, |
@oferwald Unfortunately that does NOT solve the problem on https://mathurincordier.fr. |
Hi @dleigh ,please provide the following information when you have the tpedit parameter in your url:
|
Finally understood you, you know the saying - when you explain slowly, I will understand quickly. The reason that you see nothing when translate in default language is enabled, is probably a misunderstanding about what that feature really is. The feature allows you to translate non-default language blocks on your default language. An example for that would be a comment posted in your site where the language was English, and now you are looking at it in the French language, so it is translated from English to French. It is possible to get the effect that you wanted, although I am not sure it will be what you wished for. What you will need to do is to do a dummy wrapping of your content, by using a <lang="XX"> (yes, XX, don't replace it) tag to wrap the content you wish that will be "Translatable" on your default page. There is normally no reason to do that, because the original content may simply be changed, and it does not need to be translated. LMK |
Ah - thanks for the explanation. That helps. To restate, it's about Transposh doing the translation of these non-standard blocks, NOT about facilitating the EDIT of those translations - do I have that right? |
Yes, you have that right, but naturally, you can not edit that which was never translated. |
Hi Ofer,
On https://jem-cevennes.com, I'm not seeing the frontend translation dialog when I choose to edit the translation on a default language page. French is the default language and I have "Allow translation of default language" checked, and I'm trying to edit a page that's in French. The dialog DOES show up on English pages (NOT the default language).
I'm signed in as an admin and I have the "Edit translation" checkbox. When I check it, it refreshes the page and adds "?tpedit=1" to the URL. In the dev tools (Firefox), there are no errors in the console and in the network tab, both the tranposh.js?ver=1.0.9.3 and transposhedit.js GETs have a return code of 200. So it looks like everything should be functioning. The site is running on the OceanWP theme (child-theme) and uses Elementor as a page builder.
I've gone through all the settings, but I can't help but think I'm missing something obvious.
Any ideas?
Thanks,
David
The text was updated successfully, but these errors were encountered: