Hello Erik,
that is a good idea. I’ll try to get this feature into the next plugin’s version, which will be published in about two weeks.
That would be really great!
Erik
Would you please download and install the 3.14-beta1 version from here and test the permalink slug functionality?
Let me know if you find any bugs or issues.
If everything works alright, then you can continue using the 3.14-beta1 version until updating to the new version.
Works like a charm… many thanks!
Erik
Ok, then I’ll add the feature in the next 3.14 version.
Hi Diana,
I noticed that an extra CSS permalink option is now showning when editing standard pages and posts. Think this is not correct, could you verify that?
Erik
Yes, that is an error. I forgot to limit it to Add/Edit Custom Code pages.
If you update to the 3.14 version, then you’ll see this corrected.
I’ve playing with this also, the custom slug works and there is a .css file created in /wp-content/uploads/custom-css-js/
But the .css with the custom slug filename is not loaded on the website.
The original .css with the postid as filename is still there and is still loaded by the website instead.
Deleting the .css with postid filename does not make the .css with custom slug filename load in it’s place.
I had the edit page for that css code still open and clicked the button to save/apply and it re-created the .css with postid filename. Website back to normal.
Can you confirm @evdheuvel and @diana_burduja ?
-
This reply was modified 8 years, 1 month ago by
kahana82.
Yes, the custom slug is there only to help you link it from another website.
It was not meant to delete/replace the file with the custom code id, not it was meant to be loaded on the website with that custom slug name.
I understand the current functionality, but it would be neat/logical to have it behave as I mentionned … I’m a bit OCD perhaps, please forgive me 🙂
It works (great) as it is but maybe this behavior ca be added in a later version ?
I’ll put it on my TODO list and consider it for the next plugin’s version.
