mputman007

@auctollo I suggest you FIX YOUR PLUGIN. It is what is adding the .xsl file when it is installed. Honestly your reply above that just parrots the Google Search Console errors and how to fix them is LAZY and also will not fix the problem. Be a better developer and fix your plugin.

Yeah, The Events Calendar never wants to acknowledge bugs in their software. I am facing this issue as well.

Wow just abysmal. 2 months between responses. We removed your plugin 2 months ago because of the errors it was throwing. Just garbage.

Yes, we verified that a month ago when the update came out. Thanks for the “timely” *ahem* update to this post.

Here is the solution that finally worked for me:
Reset Site Kit?(Tools > Available Tools > Reset Site Kit), if?“Reset sharing permissions”?option doesn’t resolve the issue for you.

You will then, have to:
1. Associate Search Console with Google Analytics (if not already done),
2. Add any Google Accounts that you want to have controlling access to this data in GA.
2. Reconnect Site Kit (and Google Analytics), using a Google Account with those admin permissions for GA and Search Console to the user that you want to have share management control,
3. Reconnect any WordPress user previously connected to Site Kit that needs more than view access.
4. All other users that have one of the roles specified in the share access “Who may View” can connect to site kit by clicking on “Skip sign-in and view limited dashboard” link in the Site Kit setup.

Well, resetting Site Kit did the trick. This should be added to the FAQs for the plugin. I would think it would save you a lot of individual troubleshooting.

I’ve been using the same email to connect SiteKit each time. It is [email protected].

Dashboard:

LOL. Sure. Google’s transition from UA to GA4 has been a nightmare for all involved. And, I will report back here the outcome, so that other may benefit. SMH.

This is not the problem. I am signed in to WordPress with the EXACT SAME EMAIL ADDRESS tied to the Google Analytics Administrator. This is the Google account used to setup Google Analytics.

The problem appears to be with the transition from UA to GA4 properties. I was able to disconnect Analytics from SiteKit and set it up again, this time attached to the GA4 property instead of the UA tag and now I have the ability to manage view access for Google Analytics.

However, even though I have disconnected and reassociated Search Console with the GA4 tag, I still cannot manage view access for Search Console. I believe this is a bug with the SiteKit transitive trust between SiteKit and the Google Search Console that is apparently created when signing in to the Google account when connecting SiteKit. Further, since there is no way to remove Search Console access only in Site Kit to perform a similar reconnection to only that service like I did for Google Analytics, I cannot solve that access issue the same way.

I have already done that twice.

This does not work if you are not the owner of Google Analytics, which most website administrators are not.

I don’t want to get over 100 notifications for my customers. I connect the Site Kit to each WordPress console with their GA credentials. In this use case the Site Kit fails.

This answer does not solve the issue.

“Contact managing user to manage view access.” persists after resetting sharing permissions.

No, it is not good, not at all. I have already reached out to the dev team behind The Events Calendar Shortcode & Templates Pro, but here’s the thing. The Events Calendar (and contributors) are always quick to point the finger at someone else. You DO have control over compatibility with third-party add-ons and customizations. All you have to do is work WITH add-on and web developers DURING the development cycle. You see us as competition. You should see us as business partners.

6.0.0 worked just fine with The Events Calendar Shortcode & Templates Pro plugin (also works with 2.9.3), but obviously, something changed between 6.0.0 and 6.0.1 with regard to the naming of the event title, since now it pulls that page name for all events. We’re digging into their plugin to try to fix it. You could be “super useful” if you could tell us with constants in functions changed between 6.0.0 and 6.0.1.

This happens a lot, so much so that there are several knowledge base and troubleshooting posts (https://theeventscalendar.com/knowledgebase/k/custom-templates-custom-hooks-and-upgrading-to-tec-6-0/ and https://theeventscalendar.com/knowledgebase/k/calendar-page-shows-event-title/ to name two to them) located on The Events Calendar website regarding changes to function contant names that have caused customization and compatibility issues.

This is a poor practice (and probably not a micro “dot release”) to keep renaming constants in your plugin, especially if you are not going to put the specific information in the release notes. It almost ensures that web developers and third-party plugin developers will stop trying to chase nearly continuous compatibility issues to add the customization functionality that should already be included in the plugin. Especially so, for the price you are charging for the plugin.

So, why don’t you be “super useful” and try to work with the community buying your plugin instead of the all too often, shoulder shrug?

• This reply was modified 2 years, 2 months ago by mputman007.

This would be good information to include in the MailPoet Sending Service FAQ. It does not exist and is essential information for those using your plugin. You should also mention the IP block (176.9.183.0/24) that the MailPoet Sending Service uses and that they come from Amsterdam, The Netherlands, so that subscribers do not block incoming email from those locations.

Turning off Dynamic CSS fixes the space at the top of the page. However, it does not fix a new issue with the photo carousel not advancing on the individual listing pages, or the map, schools, and walk score tabs being blank. I have viewed @rowdycolors website above and it is experiencing the same issues as our real estate clients’ sites.

Here is an example of one of our clients” pages that is not working:

https://teamham.com/property-details/730-NEW-HAMPSHIRE-LAWRENCE-KS-66044/154980/489/

The Updated Calendar views are a total disaster. Why couldn’t you just leave it alone? It was working.

Now, none of the shortcodes work with the Updated Calendar views (v5.7.0). we were using those in DIVI so that we can use a custom global section as the footer, which we cannot do with the default /events/ calendar view.

The shorecodes need to be fixed and stable BEFORE you kill off the legacy views (currently scheduled to happen August 3rd.)

The pro version of the plugin costs too much for this to be a constant issue.