Forum Replies Created
-
AuthorPosts
-
Leah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahJanuary 21, 2014 at 3:02 pm in reply to: Bug in MapView – "Uncaught RangeError: Maximum call stack size exceeded" #95363Leah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahJanuary 21, 2014 at 3:02 pm in reply to: tribe-event-placeholder should not have microformats applied to it #95362Leah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahJanuary 21, 2014 at 2:58 pm in reply to: Wrong gettext-domain in venue.php preventing translation #95351Leah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.
Best,
LeahLeah
MemberHi there,
I’m happy to report that we have fixed this in our upcoming version 3.4. Keep an eye on your Plugins page for an update message! Thanks for your patience while we worked on this.
Best,
LeahLeah
MemberHi there,
I’m happy to report that we have fixed this in our upcoming version 3.4. Keep an eye on your Plugins page for an update message! Thanks for your patience while we worked on this.
Best,
LeahLeah
MemberHi there,
I’m happy to report that we have fixed this in our upcoming version 3.4. Keep an eye on your Plugins page for an update message! Thanks for your patience while we worked on this.
Best,
Leah -
AuthorPosts
