Closed GoogleCodeExporter closed 8 years ago
I can't reproduce this. What were the exact names you used?
Original comment by ever...@fireproofsocks.com
on 6 Aug 2012 at 3:03
Post type: order
Menu name: "Онлайн заявка" in bulgarian language.
Original comment by maria.se...@gmail.com
on 8 Aug 2012 at 5:03
Thanks for the details. "order" might be a reserved word since it is also a
database command. I found some other words that WordPress does not play nicely
with. E.g. trying to name your post-type "preview" caused weird problems, so
I had to add some code to prevent restricted words.
Original comment by ever...@fireproofsocks.com
on 8 Aug 2012 at 5:38
[deleted comment]
[deleted comment]
Hi,
Just had the same issue... I spent a lot of time thinking about the structure
of the website, built all the content types, fields. Then today I had the
excellent idea to create a content type named "actualite". When submitting I
had "Invalid content type" and a Back button.
Clicked Back, every configuration informations (fields + content types) was
erased.
ARE YOU SERIOUS ?
Original comment by thomaset...@gmail.com
on 6 Sep 2012 at 4:53
Sorry for the trouble. I would kindly request you to keep sarcasm out of the
bug-tracker. My initial attempts to reproduce the problem have been
unsuccessful, but I promise that once I can find the bug, I will patch it and
update my unit tests so the issue does not occur again. If you need an
immediate fix, please contact me privately and I can send you a quote.
Original comment by ever...@fireproofsocks.com
on 6 Sep 2012 at 4:58
[deleted comment]
After some few investigations. The problem isn't because of the "post_type".
This is because I filled "Actualité" in the menu name and apparently utf8 is
not supported when you serialize the array before it is saved in db.
Original comment by thomaset...@gmail.com
on 6 Sep 2012 at 6:45
Thanks for sharing the additional info. It's actually WP that serializes data:
that's how it stores options, but you're right: that can cause trouble with UTF
characters (e.g. see Issue #88 for related discussion). Perhaps the
CCTM::charset_decode_utf_8() function can help with the post-type name as it
did in issue #88.
Original comment by ever...@fireproofsocks.com
on 6 Sep 2012 at 6:49
I worked to reproduce this on my dev server, and I cannot: I'm able to name my
post-types using utf8 characters in both the post-type name and in the Menu
name. The post-type name replaces utf8 characters with "_", and the menu name
saves normally. See screenshot:
https://img.skitch.com/20120926-kjq4ei4x2c9q941712defjaajj.jpg
This might have something to do with the environment. If someone can provide
me access to a server where this issue is occurring I can reopen the ticket,
but right now I can't fix it because I can't reproduce it.
Original comment by ever...@fireproofsocks.com
on 26 Sep 2012 at 8:03
Original issue reported on code.google.com by
maria.se...@gmail.com
on 6 Aug 2012 at 12:00