- This topic has 6 replies, 3 voices, and was last updated 10 years, 8 months ago by .
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › eStore – Apostrophes Create Slashes In Category Names
Tagged: apostrophe
I’m just returning to eStore after some time using a third party solution (Gumroad). I’m pleased to support you guys and I hope this problem is easily resolved.
Entering a category name with an apostrophe (for example, “The Shaper’s World”) results in a category name of “The Shaper’s World.”
Additionally, each time I edit the category, an additional slash is added to the category name.
I’ve seen other users post about apostrophe problems, but they seem to have been resolved long ago and in versions much older than mine. I’m running version 7.0.7 of the plugin.
The URL this is occurring on is a non-public development space. WordPress 3.8.1, PHP 5.3.10-1ubuntu3.9, mySQL 5.5.31-0ubuntu0.12.04.2, Apache 2.2.22.
Thanks in advance for swift resolution of this problem!
Best,
Matthew Wayne Selznick
Since you are doing this on an offline server; all we can do is “guess” at things you can try…
Try replacing the apostrophe with either:
—> & r s q u o ; <— (no spaces)
or
—> & # 1 4 6 ; <— (no spaces)
Hi wzp,
It’s not an offline server, it’s just not a space I want to make public just yet.
In any event, both of your options worked… but the question remains: why doesn’t eStore parse apostrophes in categories? Seems to work in product names an elsewhere in the plugin, and certainly works elsewhere in my WP installation.
Any ideas? Love to hear from the devs, too.
Thanks again!
eStore should be able to handle it. I will look in it and make necessary changes.
Thanks, admin! I noticed it does it in the PayPal Settings page (Customize the Return Button Text) section, too… so it might happen elsewhere, as well.
We have update the plugin so this issue won’t be there in the next build.
Excellent, super-fast support. Looking forward to the next update. Many thanks!