Hi, I'm working on a website with a blog and my client wants to have a similar design in all blog posts ( Ex: blue links with underline on hover, same font everywhere,... ) BUT there's many authors that force their own style with the editor tool and even when they want, they can't remove the inline style easily. Is there a way to disable styles in blog editors tool so the stylesheets of my theme and templates will work proprely ? styling tools     Here is an exemple of junk style I see everywhere. I removed text inside for privacy. <p style="text-align: left;"><strong></strong></p> <ul style="font-size: 18px;"> <li style="text-align: left;"><a href="#" rel=" noopener" style="font-weight: normal;"></a></li> <li style="text-align: left;"><a href="#" rel=" noopener" style="font-weight: normal;"></a></li> <li style="text-align: left;"><a href="#" rel=" noopener" style="font-weight: normal;"></a><span style="font-weight: normal;">？</span></li> </ul> <p><span style="font-size: 12.0pt; color: black;"> <img src="#" style="display: block; margin-left: auto; margin-right: auto;"></span></p> <p><a href="#"style="text-decoration: none;"><span style="font-size: 12pt;"></span></a><span style="font-size: 12pt;"></span></p> <p><span style="text-decoration: none;"><span style="font-size: 12pt;"></span></span></p> <p><span style="text-decoration: none;"><span style="font-size: 12pt;">&nbsp;</span><span style="font-size: 12pt;">“</span></span></p> <p style="margin-top: 0mm; margin-right: 0mm; margin-bottom: 0mm; padding-left: 0mm;" At least something more like the Slack App editor would be better ... View more

The HubSpot-generated sitemap can only be hosted at [subdomain].[yourdomain].[tld]/sitemap.xml - for example: www.yourdomain.com/sitemap.xml   This is fine when using CMS Hub Professional. It's fine when using CMS Hub Enterprise without reverse proxy. It can become very problematic when using reverse proxy.    If, for example, you're using reverse proxy to put your HubSpot-hosted content on www.yourdomain.com/hubspot-hosted-content then HubSpot will still try to put the sitemap at www.yourdomain.com/sitemap.xml    In many reverse proxy situations, you are likely to want three sitemaps:  - the first for the domain as a whole (www.yourdomain.com/sitemap.xml) (which will just show where to find the other two sitemaps) - the second for the content hosted outside of HubSpot (www.yourdomain.com/non-hubspot/sitemap.xml) - the third for your HubSpot-hosted content www.yourdomain.com/hubspot-hosted-content/sitemap.xml   At the moment, this isn't possible, which causes significant limitations with the new reverse proxy feature.  ... View more

Native HubSpot image modules should have the option to add loading attributes to the resulting <img /> tag produced in the HTML markup. According to Can I Use... roughly 70% of users globally are using browsers that support the native loading attribute, and the attribute does not hurt user experience or SEO on older browsers. The attribute could be implemented similarly to the width and height attributes in the current image module, however instead of a number field could be displayed as a select field with options for "auto" "lazy" and "eager." As of right now, to implement lazy loading on a template built with the visual builder, a custom module needs to be created to add lazy loading functionality. Then, all existing image modules must be replaced and repopulated using the new version. A simple toggle would save developers and marketers a significant amount of time by eliminating the need for that content re-entry process. ... View more

Pretty self explanatory.   I understand that I'm able to somewhat manually build this functionality with a custom module, but it does seem strange that this is not supported officially. ... View more

Would love the ability to add content filtering into the Page module field and increase the call limit for supporting functions such as content_by_id Something akin to ACF's Relationship field.  The Page module field allows for the acquisition of any content’s ID (Page, Landing Page, or Blog). This is great, however, it could be improved by filtering what content appears in the module. This narrows what might appear, making it easier for clients to find the content the’yre trying to add.   Additionally, the documentation for the Page field does not mention Blog Posts despite the ability to select them with that field. I understand there are other functions for selecting blog posts, but sometimes you need "everything."   Functions that support the Page module field (https://developers.hubspot.com/docs/cms/hubl/functions#content-by-id)  should have higher call limits as well. Ten calls per page really limits what you can do with them. Why not give these fuctions the same limit as blog_recent_posts (200)?     ... View more

I’ve been looking at the issue of manipulating Hubspot date/time properties a lot of the community discussions around the topic. After some experimentation I’ve come to the conclusion that datetime based property calculation is possible using a little brain surgery – and within some limits – and that proper support for such functionality seems very possible – perhaps even an imminent upgrade.   It’s worth noting that others have working on filling this gap with some clever app integrations – such as https://app.hubspot.com/ecosystem/6893619/marketplace/apps/marketing/analytics-data/integration-agent-days-between-198202 which underscores the true demand.   My project began when I needed to calculate the end date of a contract, represented by a Hubspot Deal object, based on the start date (potentially different from the deal close date) and a contract term in months. I’ve no doubt, based on the community discussions, that similar business logic & workflow challenges exist for Contacts and other Hubspot object types that can be addressed by the approach described below.   The building blocks for calculating dates are as follows: - The calculation property type. https://knowledge.hubspot.com/crm-setup/create-calculation-properties At the time of writing, the documentation on this was dated 23rd Jul 2020, but it’s not clear when the current functionality was added. - The API endpoints that permit a PUT and PATCH operation to a Hubspot object type. https://developers.hubspot.com/changelog/patch-method-for-updating-crm-object-properties - A tool to manipulate the API like Postman https://www.postman.com - The knowledge of the Unix epoch time approach behind time and date stamps in Hubspot https://www.epochconverter.com/ and the date and datetime property types used to store this behind the scenes.   In order to create a calculated datetime property, its necessary to use the API to configure the property manually using a tool like Postman. The combination of property variables required seems to include a “type” of datetime and a “fieldType” of calculation_equation plus setting “calculated” to be true. Overall the data structure is likely to look like this: Regular datetime and date values can be used by the calculation property “time between” option to arrive at a difference between two dates. The result of this is a number type property which is the number of milliseconds between the two inputs. For enquiring minds, this is a multiple of 86,400,000 representing a day in Unix millisecond time.   My simple calculation required a fixed date input (Start Date) and a number of months (Term) to arrive at the calculated End Date. I used a “time between” calculation (between Unix Epoc and Start Date) to create a number value representing the Unix version of the start date, then set up the End Date as a calculated datetime property that uses a “custom equation” with the Term number (and some large constants) to create the right value. This date can then be displayed and used as a normal datetime property elsewhere in Hubspot. My first report that used this property was one that alerted the team to contracts that expired in the next 60 days and I’m sure there will be many more.   Limitations and fragility that I’ve found to be wary of: - dates can only be properly used if datetime values are rounded to the start of a day. Things that break if you don’t observe this limitation are filters in reports and views and even workflow copies from datetime to datetime properties. If you want accuracy in turning numbers of months into times difference in milliseconds, then the multiplier 30.417 used in a naïve way results in values that are not sufficiently constrained and will cause downstream app errors of various sorts. - It’s still annoyingly restrictive not to be able to use a workflow copy operation between a datetime and a date object. - To properly use a fixed time reference, such as the Unix epoch, a property much be set manually or via a workflow to the required fixed date. It does not seem possible to default a property to a zero or other fixed value in a conventional way. If you use a calculation (say =1-1) to set up a fixed datetime property value, there’s an odd limitation that prevents the fixed property being used in a “time difference” calculated property. - There’s an arbitrary limit of 5 on the number of calculated property values that can be used (at least in the Professional platform). I can’t find any documentation that mentions this, but it may be a function of the platform tier. - Given the unsupported nature of this brain surgery, it could become unusable at any time as a side effect of other updates or being locked down by product managers for whatever reason.   My plea after this effort is for Hubspot to build upon what clearly is a mostly working framework and make a set of date calculation functions available to the average user. ... View more

I would like to be able to create my own personalized drag and drop email templates in the design manager. So instead of starting to create new drag and drop templates from scratch each time and adjusting them to the CI guidelines OR cloning templates which I have created according to CI, I want to build the basic templates by using the design manager. This way, users can select from my company-specific templates when creating emails (rather than choosing the five templates provided by HubSpot) and they are still able to be creative and do their dragging and dropping, but with certain design limitations.    This functionality is essential for large companies in order to ensure that CI guidelines are being adhered to. If not implemented, the drag and drop is basically useless. Also, simple cloining of drag and drop emails won't do the trick: Just think about the end of the year when the copyright date needs to be changed. This needs to be coordinated by using a global module (just like in the old Design Manager). That's just one of many exmaples where the new drag and drop reveals its weaknesses.      ... View more

Now that the latest versions of Safari, Chrome, Edge, and Firefox all have compatibility with the .webp image format, it would be really good to have automatic image resizing for that format so that we can remove the "Serve images in next-gen formats" warning on PageSpeed Insights. ... View more

By default, it seems impossible to use functionality like 'Blog content' modules and 'Smart content' in custom modules. Since the release of the 'Local development beta' we have a lot more possibilities to create innovative and dynamic websites. Using techniques like React, ES6 and SCSS with webpack and gulp is one of the main reasons why I am so excited about the new dev beta. Custom modules alow us to set really specific purposes for modules and restrict the user on how the module is used. It also gives us the possibility of creating a complex structure for a module. This being said, the downside of using custom modules is the lack of functionality. Our marketeers want to use 'Smart content' for custom modules to benefit of all the marketing tools Hubspot has to offer. Right now, we can not use this functionality with custom modules, so we would have to use the 'old way' and use Hubspot default modules. This makes it much harder to create complex designs. We also use custom modules for our blogs. One of the most important fields in a blog is the 'Blog content'. It is used for the RSS feed and offers other functionality. We can not use this functionality in a richtext field in a custom module.   I would love to get the same functionality in custom modules. The meta.json (https://designers.hubspot.com/docs/tools/local-module-development) allready offers some settings to define what functionality and restrictions a module should have. It also has a  smart_type field, but I am not sure what the functionality of this field is. ... View more