Events Made Easy › Forums › Bug fixed or feature request implemented › yikes — all our ticket prices are not showing because of the dollar sign
Tagged: dollar sign
- This topic has 16 replies, 2 voices, and was last updated 11 years, 2 months ago by
Anonymous.
-
AuthorPosts
-
Thu 30 Jan 2014 at 00:08 #44087
Anonymous
InactiveI’m not sure how long ago this started being a problem, but for most events we list ticket prices, and they’re now not showing. I’ve just updated to the current release (1.2.4) and it’s still a problem. We have a year of events—too many events to go into each one and escape the dollar sign (besides, that’s a hack). For examples, here are a couple events:
http://www.francocenter.org/events/53/erica-brown-and-the-bluegrass-connection/
Notice that they read something like “TICKETS (General Admission): advance / at the door “? There should be dollar amounts before “advance” and “at the door”
Is there something I can edit to fix this? Any help appreciated!
Thu 30 Jan 2014 at 09:10 #50827Franky
KeymasterNow that’s weird. EME doesn’t touch event text in any way, so I’m guessing something else in wordpress is doing this. On my site everything works just fine, so you might want to try to disable other plugins one by one until you find the guilty one.
Maybe I’m overlooking something, but here it works just fine …
Thu 30 Jan 2014 at 16:52 #50828Anonymous
InactiveThis is odd. It’s not happening on any other page, just event pages. And when I turn off every other plugin, it’s still a problem. I’m stumped.
Thu 30 Jan 2014 at 16:57 #50829Anonymous
InactiveActually, it is happening on other pages when event summaries appear, such as the homepage for the comedy series on Feb 7 (http://www.francocenter.org). We had to escape the dollar sign because it’s on the homepage and coming up next—but otherwise the dollar amounts don’t show. So it’s only happening in EME events—whatever page they’re on.
Thu 30 Jan 2014 at 20:09 #50830Franky
KeymasterOk, I’m able to reproduce it: seems to be only if you have “$” followed by a number …
Thu 30 Jan 2014 at 20:34 #50831Franky
KeymasterThu 30 Jan 2014 at 21:58 #50832Anonymous
InactiveGreat!! So can I just replace the contents of those files with the contents provided? Will this also be included in the next release or will I have to manage those files separately?
Thu 30 Jan 2014 at 23:01 #50833Franky
KeymasterJust replace the strings in those files (preg_replace lines being replaced by str_replace lines) and you should be good to go.
There are some other minor bugs being resolved and then I hope to release on Sunday.
Fri 31 Jan 2014 at 14:11 #50834Anonymous
InactiveSuper. Thanks for your help!
Fri 31 Jan 2014 at 14:59 #50835Anonymous
InactiveAh, well, this worked to fix the prices (yay!), but it seems to have introduced a new problem. It looks like it might have to do with custom attributes.
Here’s what the page looks like with missing ticket prices:
http://www.francocenter.org/events/53/erica-brown-and-the-bluegrass-connection/
And here’s a snap of what that event looks like after the fix:
http://www.francocenter.org/ticket_prices_fixed.jpg
I use an attribute as a class to hide that date span when it’s only one day long, but if the attribute is missing, it shows and appears broken because of other attributes.
Fri 31 Jan 2014 at 15:38 #50836Franky
Keymasterit seems more like everything with “{” is not being replaced now. Let me check …
Fri 31 Jan 2014 at 15:41 #50837Franky
KeymasterChanging everywhere
$orig_result = preg_quote($result,'/');
into
$orig_result = $result;
fixes that … but I’m going back to check why I switched to preg_quote+preg_replace in the first place.
Fri 31 Jan 2014 at 16:01 #50838Franky
KeymasterI think it was a bordercase with single letter-replacements. So for now, I’ll switch back to the less cpu-intensive str_replace and I’ll remove the preg_quote later this evening.
Fri 31 Jan 2014 at 18:29 #50839Franky
KeymasterOk, the last part of the fix is here:
Fri 31 Jan 2014 at 23:31 #50840Anonymous
InactiveUnfortunately, I changed
$orig_result = preg_quote($result,’/’);
into
$orig_result = $result;
and the ticket prices do not show.
Sorry to be presenting such an unsquashable bug!
Fri 31 Jan 2014 at 23:40 #50841Franky
KeymasterNo no, you need to do both changesets: the preg_replace=>str_replace one and the one removing the preg_quote.
Mon 3 Feb 2014 at 23:56 #50842Anonymous
InactiveAh, I get it. That did the trick. Thank you!!
-
AuthorPosts
- The forum ‘Bug fixed or feature request implemented’ is closed to new topics and replies.