Stray Speech Marks in Widget

[Angela]

Hello there

Using the widget there appears to be a stray " on the link.

for example

Bramley Community Centre,

Is this something you can help with?

Thanks

[Angela]

<span class="tribe-events-venue"><a href="http://leedsdirectory.org/venue/bramley-community-centre/" title="Bramley Community Centre," "="">Bramley Community Centre,</a></span>

[George]

Hey @Angela,

Sorry to see this!

I don’t have this issue on my site, so I’m wondering if we can get started here by doing the following things:

1. Share your site’s “System Information,” which you can learn how to do on this page https://theeventscalendar.com/knowledgebase/sharing-sys-info/. Post that information and I’ll take a look.

2. Next, can you confirm exactly how this widget is added? Is it simply dragged into place in the “Appearance” menu in your wp-admin? Or are you using custom code of any kind to generate the widget?

3. Finally, for now—activate a default theme like Twenty Sixteen, then take a look at the widget HTML like you have in your screenshot. Do you see the same problem?

Thanks!
George

[Angela]

This reply is private.

[Angela]

This reply is private.

[Angela]

This reply is private.

[George]

Hey Angela,

In your last reply, you shared the responses from “the council”, which cite some JavaScript errors.

Can you confirm if all of these same errors show up if you activate a default theme like Twenty Sixteen on your site, and then look for the same issues?

Thank you!
George

[Angela]

Hi George
Thanks for getting back.

I will have to wait until outside working hours to switch themes and will let you know ASAP.

Thanks

🙂

[Angela]

This reply is private.

[Angela]

This reply is private.

[Angela]

This reply is private.

[George]

Thank you for the updates, Angela. This seems to be the status of the issue, to the best of my knowledge:

1. I cannot recreate your issues.
2. We have no reports of any similar issues.
3. The issues go away in the Twenty Sixteen theme.
4. You’re able to fix some of the issues with a specific, idiosyncratic customization.

So, with all of these points in mind, it is clear to me that the issue is not arising from within our plugin code ourselves; your theme and/or some combination of other factors arising from the level of the server are breaking things.

These facts mean that there is little we can do here because we do not make your theme and do not make your sever.

From here, if you would like to get a refund you can definitely do this if your purchase was made in the last thirty days. Here’s how to do that → https://theeventscalendar.com/knowledgebase/refund-policy/

Aside from a refund, though, there are no moves on the board for us and so you’d have to take the reins on this issue from here. 🙁

I’m sorry to bear this disappointing news but just wanted to describe the current situation and be frank about our ability to help with this theme/server-caused issue.

Thank you for your patience and persistence in this thread.

Sincerely,
George

[Angela]

Hi George

The above paragraph appears to be very much copy and paste?

As I have reported to you it is not an issue with the theme it is an issue with BrowseAloud and has only occurred after the last couple of updates you released. Up until that point everything was working fine so from my point of view the updates you have released are currently incompatible with BrowseAloud which is a product we have had installed for the last 2 years.

Perhaps you cannot recreate the issues or have not heard of them because your other customers do not use BrowseAloud?
https://www.texthelp.com/en-gb/products/browsealoud

The issues would perhaps still be there if I had TwentySixteen installed and the javascript for BrowseAloud was added to a text widget. The only reason it didn’t occur when switching themes is because it was hard coded into the footer. Maybe that should be tested?

<script type=”text/javascript”>var _baLocale = ‘uk’, _baUseCookies = true, _baHiddenMode = false, _baHideOnLoad = true;</script>
<script type=”text/javascript” src=”//www.browsealoud.com/plus/scripts/ba.js”></script>

I am not quite sure why you mention the server? I realise you do not make either theme or server however the issue is neither of those.

Until I have tested this with TwentySixteen and the BrowseAloud javascript added then I would like to keep this thread open.

Sincerely

Angela

[George]

Hey Angela,

Thank you for clarifying that the issue is more with BrowseAloud than the theme. Earlier you said, “As I thought no issue there with 2016,” and I took this to mean that doing nothing else on your site but activating a default theme resolved the issue.

Seeing that BrowseAloud is fundamentally and accessibility tool, I would love to see our plugins behave better alongside it.

I have looked at http://leedsdirectory.org/ to try and better identify/understand the JavaScript issues in hopes of being able to recommend something to fix the problem; I unfortunately have not been successful in doing so.

So from here I will have to raise this as an issue for our developers to investigate—to be candid, we are in the midst of active development for the next release and so this would not get attention for at least a few weeks. I’m sorry about this but wanted to be honest about the expectations here.

The problem remains that the cause of this issue is a third-party piece of software that we do not make, so the best thing to do is reach out to the BrowseAloud folks directly and see if they can explain why their code breaks other website features. While I cannot guarantee a successful outcome here or a satisfactorily-rapid pace, we can investigate this in the meantime and see if there’s something on our end that we can do for this issue.

Thank you,
George

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts