cheffernan

Hi @arjean,

The issue is now resolved. The tagging will be correct as of version 11.1.6 which was released today.

Best,

Conor

Hi @damonmaldonado ,

Thanks for the information. I have tried to reproduce the bug by installing:

• installing the beaver blocks plugin on my wordpress instance
• creating a page using the beaver blocks plugin
• modifying this page using the standard Gutenberg block editor

When I do this however I am not encountering the error shown in your screenshot. I will need more information to help understand the issue more. Three debugging steps you could take to help me understand the nature of the issue would be:

• Does this issue happen for pages not made with beaver blocks? : Could you create a new page (not with beaver blocks) and try to edit this using the Gutenberg editor. Do you still see the same issue?
• What are the exact steps that caused this error? Could you take a screen recording of creating a new page using beaver blocks and then editing in the Gutenberg editor. As I was unable to reproduce this error, this would be helpful in understanding how you are triggering the problem that you are experiencing. You can send the screen recording to [email protected].
• Capture errors and send to us: Console / Server logs could be helpful here. If you could take a screen recording of when you encounter the error if there are console log errors happening that you think are related to this issue that would be helpful. Alternatively if there are no console logs that would be helpful, it is possible that server logs may have some information about the nature of the problem. If you can access PHP error logs for your wordpress instance you can send them to [email protected]
  

Best,

Conor

Hi Arjean,

It appears there is a bug with our deployment pipeline. We are looking into it. Thank you for drawing our attention to this issue.

Best,

Conor

Hi @dleigh,

I am going to mark this topic as resolved. Feel free to let me know if there is anything that you think you could do with the plugin which you are unable to do otherwise.

Best,

Conor

Hi @kit21,

After some investigation we have determined that significant refactoring on the Gutenberg blocks would be required for us to support the full site editor. This work is not currently in our priorities for this quarter.

For this reason, in version 11.0.55 of the plugin (just released today) we have officially dropped support for our blocks inside the Full Site editor.

We hope to revisit this at a later date and carry out the work necessary to have our blocks function in the full site editor, for now however I am marking this conversation as resolved as the plugin officially now does not support Gutenberg blocks in the full site editor.

You should still be able to use the HubSpot blocks in the page and block editors. Please let me know if there is any page editing functionality that you would like to do which you cannot do in these editors and I am happy to suggest further workarounds.

Best,

Conor

Hi @dleigh,

Everything that you can do with the plugin, you will be able to do manually without. The plugin merely offers a convenient way to do things in one place (from your WordPress admin panel). We do offer some blocks for instance that can be used in the Gutenberg and Elementor page editors for instance but again, the HubSpot forms and HubSpot meetings links that are offered in the plugin can be added manually.

I will include some links below of how you can complete some of the actions offered by the plugin once the tracking code is installed.

1. Adding forms to your website pages ( you can opt to use the shortcode in your page editor)
2. Adding meeting links to your pages
   
   

You will also be able to set up live chat directly within your HubSpot portal (it will then be added to your website automatically by the tracking code).

Best,

Conor

Hi @dleigh,

Sorry to hear there is a conflict between the WooCommerce anti fraud plugin and the HubSpot plugin. Unfortunately we cannot guarantee interoperability between our plugin and every other plugin on the plugin store.

If you could isolate and describe to us the precise nature of the conflict in technical terms (for instance which requests are failing and why) with a suggestion of how this conflict can be avoided then we may be able to help depending on the nature of the problem.

In lieu of this, I would suggest that you could try using the HubSpot tracking code directly rather than relying on the plugin to add this to your site. You can read steps to do this in this knowledge base article .

Apologies I cannot be of more help right now. I hope you can appreciate that there are more than fifty thousand plugins available on the plugin store, while we are happy to do everything we can to fix bugs in the HubSpot plugin, without a more precise remit it’s infeasible for us to invest the time and money required to isolate the cause of such issues.

Best,

Conor

Thanks for the info @kit21, that is very helpful. We have been able to reproduce this on our end.

We are investigating possible workarounds for this problem now. You mentioned specifically webpack imports with a relative path will be broken. Are you implying here that in your opinion if we replace relative imports with absolute imports this should resolve the issue?

Best,

Conor

Hi @kit21

Sorry to hear you are having issues with the HubSpot blocks. Hopefully I can help debug the issue but I will need some more details from you.

Would you be able to send me:

1. The version of the plugin you have installled
2. The version of PhP that your site uses
3. A screen recording of the problem that you are having
4. an error messages in your console logs or network tab.

I look forward to hearing from you soon.

Best,

Conor

Hi @bindslind

Have you tried modifying the form on your webpage to use the on ready callback? You should be able to dynamically load your google script in here to make sure that the form load proceeds the script ready. Docs here.

This support forum is more geared towards responding to technical problems with the HubSpot WordPress plugin rather than general troubleshooting with HubSpot forms or any other specific HubSpot feature which is outside of the remit of the team maintaining this support forum. For follow up / additional help with this I would direct you to the HubSpot Community Page which features a discussion forum where community members can offer help / guidance / support on issues such as these.

Best Regards,

Conor

Hi?@mateostrasdas,

I have been in contact with the relevant product team and can confirm that this continues to be something that HubSpot is working on improving. While the suggestions mentioned above are the viable options right now, in the medium term I anticipate this issue improving without any action from your side, particularly with respect to forms.

There is no definite timeline on when this change will happen. It is an ongoing project. The fact that it is currently in development is a positive sign but I cannot speak to a specific date to wait for.

I’m closing this support topic as it does not relate to a particular bug with the WordPress plugin. If you would like to discuss this further, I would direct you to the HubSpot community forum which provides a more appropriate platform to discuss topics related to HubSpot in general. It is possible that you might find a discussion here relevant to your particular situation which could ameliorate the issues you are having with the HubSpot analytics script in relation to the PageSpeed report.

Best,

Conor

Hi @mateostrasdas,

Thank you for contacting us. I am sorry to hear that your site is being impacted by the plugin on PageSpeed Insights. I would like to preface this answer by saying that one thing to remember about performance recommendations surfaced in tools such as lighthouse is that they do not always make sense. External tools typically use bots and automated measures to evaluate a site and assign a score or grade. When thinking about your website we believe it is better to make decisions with the visitor’s experience at the forefront, not a bot’s experience.

The reality is that loading the HubSpot tracking code will have a non-zero impact on your website’s page speed. This is a trade off of having the script on your website. However there are some things I can recommend to minimise this impact.

If you are not interested in having HubSpot analytics on every page on your website, you can remove the tracking code from loading on every page on your website by deactivating and removing HubSpot WordPress plugin and then manually installing the tracking code on pages that you are interested in having HubSpot analytics on (using these instructions).

Alternatively, If you are using live chat, you can set the time on page in seconds trigger using the steps detailed in the linked guide. Setting this to at least 5 seconds will delay the live chat being loaded and should improve your initial page load speed.

I would also audit your HubSpot portal and check that all the scripts being loaded by the tracking script are necessary e.g maybe you are loading popup forms but these aren’t necessarily used on your website.

For my part, this issue is somewhat outside the remit of my team (who are responsible for maintaining this plugin, not the script in question). I will bring this query to the relevant team in HubSpot and see what can be done on our side to improve this issue.

Best,

Conor

Hi Rayeason

Sure, it’s possible to do this by updating your HubSpot settings.

If you go settings -> inboxes -> inboxes -> chat -> edit

as shown in this loom you should be able to update that no problem. Let me know if you have any difficulties.

Just a heads up this support forum is more geared towards users that are having specific issues with how the plugin is integrated with their WordPress instance. I understand that your website is running on WordPress but for more generic HubSpot related questions I would direct you to the HubSpot community forum. There are tonnes of great answers here from the HubSpot community which will help you self serve at a faster pace than we would be able to respond on the WordPress plugin support forum.

Best,

Conor

Hi Thomas,

Thank you for bringing this to our attention. I will add an accessibility item to our backlog. I anticipate this issue will be resolved within a couple of months.

Best,
Conor

Hi Thomas,

Thanks for getting in touch. Would you be able to provide a little bit more context about the issue you are facing. I understand that the type attribute may be unnecessary. I am wondering if you can elaborate on:

1. What is the purpose of this “better HTML checking”? I am wondering what the optimisation gained here is? Is it reducing unnecessary bytes from your html file?
2. Is there anything on your web page that is currently broken as a result of this attribute. This will help us prioritise this task in our backlog.

Thanks for taking the time,

Best,

Conor