Forum Replies Created
-
Posts
-
Hi Brian,
after talking to my providers support, I don’t think my server is blocking yours. Could it however be possible that yours is blocking our server?
Hello Brian,
that’s the plugins output for all your URL and IP. All others (like google.com) work perfectly fine:
Checking URL: https://162.243.159.176
Error Found ( connect() timed out! )
WP_Error Object(
[errors] => Array (
[http_request_failed] => Array (
[0] => connect() timed out!
)
)
[error_data] => Array
(
)
)
Response Code ( )
Response Message ( )Hello Leah,
right now, for my running version, it’s resolved and works finde, but i’d like to see it fixed in future releases. There are quiet a few localisation issues in your otherwise great and perfect event calendar and if you guys like, i could send you a full report for all the extensions we use. 🙂
The translation files are all perfect, I can’t stress this enough! The venue.php simply isn’t pulling the right data (hope you get what i mean with my broken english…).
Hello Leah,
sorry I can’t remember the exact issue anymore (it’s been quiet a while). What I remember is:– I bought version 3.4.1 of PRO, Community and FB Import 2 days after release. They where perfectly up to date.
– The translation file (german) for Community looked perfect (both original and translated string), but it simply didn’t show up in frontend.
– Changing the strings didn’t work.
– What worked was using the tribe-event-calender translation files instead the community translation files.Right now, I can’t recreate the issue, for I don’t want to update the software at this point. I made quiet a view localization-changes that remain unfixed in the 3.4.1. (I made seperate posts for those).
Thanks,
SebastianHey Guys,
hope you don’t mind if I join in. I had the same issue (support telling me it was intendet.. :/) but Caseys fix works fine for me! But there is another issue with wrong datetimes. It’s the heading and table-header in weekly view. I uploaded a screenshot with some notes on it:https://dl.dropboxusercontent.com/u/54549103/strangedates.jpg
Here you go:
https://dl.dropboxusercontent.com/u/54549103/datetime.jpg
This happens for the widget, too, btw. Maybe your code is using another, non-localized datetime for the current year (like, without the year) than for other entries?
Hey Casey,
it’s 3.3. I bought the plugins after your last release, right before christmas. Changing the lines in venue.php worked out perfectly fine, fixing those issues. But it would be nice to include those fixes in future updates so we dont have to do it again. 🙂
Hey Leah,
yes I use the latest version. It’s just minor, i fixed it myself but i thought I should let you know…
Hey Neill, thanks for your awnser.
The problem expendet a little: Your plugin uses the right dateformat for other years than the current. Sounds a little strange, but its exactly what happens.
Let me show you two events in our calendar:
An event taking place in 2014 (happy new year, btw. ;))
http://www.helmstedter-tageblog.de/events/And here a listview including an event in 2015:
http://www.helmstedter-tageblog.de/events/anstehend/?action=tribe_list&tribe_paged=3As you can see, all 2014 Events (in 2013, it has been the 2013 Events) use (ex.) April 25 @ 20:00 as datetime, while events schedueled for 2015 display dates like 1. Januar 2015.
Greetings,
SebastianHey Neil, thanks for your response. I quess it’s a seperate issue. The “decembre”-issue expandet a little. I’ll post something more in that other thread which might help you find the awnser.
But well, it wont solve this problem here 🙁
BTW, i really love your plugins and will recommend them to all my customers if those pesky localisation quirks are solved. 🙂
