-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Traduction dosen't work with WPML #59
Comments
Hi, any update on this issue. We have the same problem. @stefanogit did you find any solutions? |
Sorry for late reply. Replace Sample code https://gist.github.com/torounit/86c3c140071d29cd1b2fd2900f23c813. |
Hello @torounit, we used your filter, in our functions.php file. We setup this file, according to your autoload rules: ./Module/Rewrite/Fix.php It seems it still doesn't works, any idea on this issue? May I ask your further help? Our CPT restaurants, still remains "restaurants" and not - for example - "ristoranti" Thank you |
Hi, @torounit, what do you mean exactly? |
I have the same problem, what does |
@torounit Are you still maintaining this repository? |
@torounit Hello! I'm interested too to follow this fix, I have same issue. Thank you for this awesome plugin! |
Unfortunately I have the same problem, is there a fix? |
Hi :-)
I installed latest version (2.0.1), I use WPML and I have a problem with the slug traduction. On WPML I checked string traduction and every option but everything looks goods.
I found this post:
https://wordpress.org/support/topic/not-compatible-with-wpml-wordpress-multilanguage?replies=4
And I tried that solution (with the new file the line is about 80) but I got this error:
Deprecated: Non-static method WPML_Slug_Translation::get_translated_slug() should not be called statically, assuming $this from incompatible context in /home/e41pymtn/public_html/wp-content/plugins/custom-post-type-permalinks/CPTP/Module/Permalink.php on line 80
Any idea?
Thanks ;-)
https://wordpress.org/plugins/custom-post-type-permalinks/
The text was updated successfully, but these errors were encountered: