1)
On the post type edit screen "Aktuelles":
- hidden link
==>
- when you try to save the post type, it shows the following message: "You cannot use this slug because it is already used or a reserved word. Please choose a different slug.".
First of all, I see you have multiple items available on your install with the slug "aktuelles". In WordPress you should have unique slugs. First of all I suggest you to change all slugs where you added slug as "aktuelles", the slug should be unique. As you already used the slug "aktuelles" for the post type "Aktuelles", you should not use the slug "aktuelles" for any page/post/view/content template name.
You should be able to save the post type without the above mentioned error.
2)
Then I suggest you update all plugins on your install to make sure you are using all latest plugin version.
3)
Please make sure that you set your post type to use the "Classic" editor and save your post type and then check if you able to see the issue.
- hidden link
4)
*** Please make a FULL BACKUP of your database and website.***
Could you please try to resolve your issue by deactivating all third-party plugins as well as with the default theme to check for any possible conflicts with any of the plugins or themes?
Hello Minesh,
Where exactly did we used aktuelles as well? We would like to keep the slug in the Post Type "Aktuelles" and want to change it where ever it appears as well.
Actually that you need to find as I'm not the one who work on the site. I suggested that based on the error I see that means you have duplicate slug conflict with your post type slug ""aktuelles". As far as I remember there was page and view whose name is ""aktuelles".
You can check your pages, taxonomies/terms, views, content templates, archives etc..etc..
Once you able to save the post type "aktuelles" successfully from post type edit screen that means there is no conflict available.
Unfortunately it would appear that a solution is not yet available for this issue. The reason for this taking so long is that the problem is related to the wordpress core itself and any solution will need to come directly from them.
This is not something that can be fixed on our end. As you can see in the comments Nigel has been actively trying to bring the issue back to the wordpress core developers so that it can be addressed.
In this case the problem seems to only occur when your child theme is active. Switching to the parent Enfold theme, the issue doesn't occur. There must be some customisation in the child theme which affects the TinyMCE editor.
Even if you disable all Toolset plugins and edit a normal Post with the classic editor, the child theme forces the TinyMCE editor to switch to the Text tab. This customisation breaks saving content of WYSIWYG custom fields in the Visual tab.
