milestone
Forum Replies Created
-
Forum: Reviews
In reply to: [Category Wise Search] Does exactly what it says on the tin!select#searchform_cat {
display: none;
}Hope that helps!
Can’t say I have yet – this site is a freebie one I am hurriedly building for an artist that exhibits at a lot of art/craft fairs etc so nobody needs to sign up/be contacted. She just needs a site that is really easy to maintain as she is def not very tech literate! (Don’t let her see that though! ?? )
But I hope, soon, on the back of it to design something more adventurous and then I do hope to use this same plugin in all its capabilities.
So great to find it is so well supported – when the next site actually brings some money in I’ll make sure some gets passed on!
Yep, just added that CSS tag to your main CSS file (probably not the best place!) and it does the trick perfectly.
Success!!!
Initial positioning outside the visual frame with CSS? Don’t have to get rid of it at all then…
But there again I haven’t looked to see how it’s all being generated ??
Very neat Franky!
Just tested it and although it works absolutely great, I was a bit surprised to see on creating a new event that, before I did anything, there was an open calendar-picker just sitting at the very very bottom left of that page (couldn’t be dragged). Selecting an actual date in the right place meant that it disappeared.
Just tried that initial date-picker on a new event and it is totally non-functional.
That line 212 again!!!
I guess the only thing to take out now is that erroneous hint about empty dates ??
Show Time! Thanks again!
I never looked in the actual database, but when I looked in the admin after uninstalling old trunk and installing the new trunk, then the already entered events seemed initially to be in the unaltered (wrong) date format. So I just repicked them and they immediately resettled into the correct format. The times were already replaced by their 24Hr equivalents do I didn’t have to touch them and a new test event had no ‘problems’ either.
As mentioned before, the front end never wavered (presumably because the actual dates are immediately serialized into the DB). Some form of cache? Certainly not a biggie!
Fantastic Franky!!!
Works now like a charm – had to quickly reset the dates on the events already in the DB, but that was nothing.
So thank you for sorting out one bug that wasn’t and one I didn’t realize was one ?? in only one day. Magnifique!
Ack, hyphens, underscores…
My site is now corrected to underscores (there’s so little diff between US and UK in WP I hadn’t noticed). I’d also corrected the hyphen to an underscore in your line 212 but as you say the datepicker js files might well throw everything so I think I’ll just wait for you to reconcile everything now!
Update:
Yep, just an unwanted extra comma before the new en-GB section on line 212.
But the corrected version still makes no difference ?? I’ve still got the default US date/time pickers.
Just double-checked and the page source confirms I am
<html lang="en-GB">, I have all the en-GB mo files and my config file is also set to en-GB.Can I ask whether anybody who is running an international version has got anything other than mdy and 12Hr? Perhaps everyone else just tolerates it?
Hi Franky
Thanks for this v speedy fix! Your attitude really shines out!
OK, I installed the dev version and I think there’s a typo in the fix:
“Parse error: syntax error, unexpected ‘,’, expecting ‘)’ in /home/scarlett/public_html/wax/wp-content/plugins/events-made-easy/events-manager.php on line 212”
I’ll take a look but you’ll probably want to fix ??
Thanks Franky – I think we can mark the End Date ‘bug’ as sorted! And the display workaround is now up here now for all to see and use ??
But for the date, my server and locale is GB not US, WP is set correctly and the rest of the site is displaying as UK norms (ie 24Hr and d/M/Y). It is just these calendar and time pickers that are not co-operating.
Does this jquery ignore WP settings and use something deeper in the server that I haven’t looked at yet?
Forum: Requests and Feedback
In reply to: earliest dates wordpress can handle .. how about 1858?Just an idea from a fellow genealogist (and it is so outside the envelope, no guarantee it is not pure rubbish!)…
Assuming this is a ‘faux’ blog with only historical characters participating so that only you can post/comment/cause anything to change a timestamp, then you could advance all your blog dates by 200 years (so that in WordPress Charles Thorp migrated in 2058.
Then you’ll have to trap the date, and then change it by a nifty piece of regex in PHP. I’m sure you will have hours of fun doing that!
Or you could hide that date entirely, and create your own ‘false’ date within the post.
Over to you to think outside the loop!
Colin