Forum Replies Created
-
Posts
-
Howdy,
I am happy to assist you with this.
1. Editing o creating events, the venue box gets block at the beggining and it doesn’t load anymore (venue also gets block in event frontend template).
This seems like a JavaScript “conflict”. In order to proceed we will need to test if a conflict is happening, and if so narrow it down so we can find a fix for it. This guide walks you through how to test for a conflict, and then identify what is conflicting.
2. Only when we activate EventsC-PRO, the widget “tribe-events-venue-widget” (“Eventos resaltados por lugar”), also blocks widgets page not loading widgets areas or whatever after this widget.
This also sounds like a conflict. Can you try testing this issue as well, and see if it is the result a conflict like the first issue?
Cheers!
– Brook
You are welcome, Pablo. I wish I had better news there.
I know some users have found things like the Filter Bar to be helpful for improving search. The Filter Bar can add a list of all of your venues to the main events page, then a user can click on one or multiple to show events from those venues. Does that sound like it might help you here?
Cheers!
– Brook
Wow! That’s some detailed documentation. I will keep this in mind for future users of the Awake theme. Thank you for sharing Josh!
- Brook
Howdy Allison,
Thanks for getting back to us. Geoff was having me take a looksie now that you have approved access, since I had a good idea of what to be looking for. When I opened up the debug bar I noticed it was not quite finished being setup. Unfortunately I can not finish the setup from my end, we will have to rely on you to do that likely via FTP. The debug bar, and most any diagnostic tool, is going to require you to enable WP_DEBUG and SAVEQUERIES. The WordPress Codex has a great guide on how to enable settings like these by editting wp-config.php. Once you have read the intro there are two sections in that guide worth reading as well, one for WP_DEBUG and the other for SAVEQUERIES. You will want to set both of these to true as outlined:
https://codex.wordpress.org/Editing_wp-config.php#Debug
https://codex.wordpress.org/Editing_wp-config.php#Save_queries_for_analysisOnce you have done that we will have some nice diagnostic information that will likely prove helpful. Please let us know if you have any questions along the way. Thanks for working with us Allison, I hope we an find you a resolution shortly.
Cheers!
– Brook
Thank you for marking answer correct. I will now archive this topic. Let us know if you need anything else. Cheers!
– Brook
Thank you for marking answer correct. I will now archive this topic. Let us know if you need anything else. Cheers!
– Brook
Howdy Robin,
Thank you for the update and all of the details. I would love to help you with this.
When a change takes a while to apply it is basically guaranteed to be a caching issue. There are numerous caches that can be the culprit, but often we only think of our local browser cache. Here is a list of common ones:
- Browser Cache
- CDN Cache
- Server cache such as a WordPress plugin or apache/nginx config
If you’re not sure if your host had automatically setup a CSDN or server cache for you, double check with them. Open up a support ticket and they should be able to fill you in on the details.
Have you double cleared each of those after making you change?
Cheers!
– Brook
Howdy Josh,
I would love to help you with that.
It sounds like “conflict” is happening, causing the post type on those views to be altered. We should test for this and narrow it down so we can find the culprit and a possible fix. This guide walks you through how to test for a conflict, and then identify what is conflicting.
Does that all make sense? Please let me know.
Cheers!
– Brook
Thank you Jeff. I am seeing some strange errors there. I am trying to find the source. I will get back to you shortly.
- Brook
Howdy Luke,
Thank you for reporting this. That’s not something we have notices before, but we would be keen to fix it in a future version.
If you do not want to wait until then, you can fix it now. The string is located in public_html/wp-content/plugins/the-events-calendar/src/Tribe/Main.php:1327 and is as follows:
Event published. <a href="%1$s">View %2$s</a>Using a snippet like the one in this tutorial, you could alter it to something else. Tutorial: Change the wording of any bit of text or string. In this case your custrom array would need to be something like this:
$custom_text = array( 'Event published. <a href="%1$s">View %2$s</a>' => 'Transfer published. <a href="%1$s">View %2$s</a>', );Does that all make sense?
Cheers!
– Brook
Hello Edu,
I would be happy to help you out.
It sounds like when you go create a new event in the WP Admin, it does not appear on the front end of your website. Is that correct? Does it eventually appear after a few hours?
You obviously have some events in the site already. Did this problem start happening recently? Did you do anything different around the time it started?
Cheers!
– Brook
Thanks for clarifying, Stacey. I was unfamiliar with with AppPresser.
It is clearly not a JS issue if that test link doesn’t work as well. What I am suspicious of is that something in the AppPresser version is causing the server to generate an error message. If there is an HTML error message output before the calendar content, then the server would be outputting it before the calendar download file. Thus you would get the error: Resource interpreted as [HTML] Document but transferred with MIME type text/calendar. On your server is display_errors and display_startup_errors turned on? What happens if you turn them off? This is a php.ini setting. If you are unfamiliar with checking and changing these, you will need to consult your website host as it is different for each host.
That’s the only thing left I can think to try. Please let me know the result.
Cheers!
– Brook
Howdy Edwin,
That is definitely possible. You have basically described Community Events (click here to view features). Community events allows you to add a page on the front end of your website, and gives you control over who can access it. If you want to accept anonymous submissions, you can. Or if you want users to register first, or only users with a certain WordPress Role. You can limit it as much as you need. Each user will only be able to modify their own events, and will not need access to the WP Admin.
Does that all make sense? Will that work for you?
Cheers!
– Brook
