Great minds think alike

TCuijpers

Hi Hubspot, There has been an update in the CMS back-end which now prevents the possibility to open multiple webpages in tabs, this is very annoying and really hinders my efficiency! Instead of opening multiple pages at once, I now have to open one at a time, which also means whenever I finish working on that particular page I need to go back, load the overview of webpages again, re-enter all my filters that I had for the task at hand and look at the big list of all our webpages where I need to continue with my task. Sometimes I need to do simple changes on say 50 pages, this used to be super easily managable by opening a handful of the pages at the same time in multiple tabs, and thus keeping the overview page with all my active filters open as well. Please, can you reconsider rolling back this feature, it is actually very bad for productivity. It is still possible on for instance the other parts in the back-end, with forms and workflows for instance. Thank you for your time, Teun

KPruett · ‎May 22, 2025

Currently, only legacy forms are available to be used in custom modules. In order to add a form created with the new form editor to a page, the only option is to use HubSpot's default 'form' module that's provided in the drag-and-drop editor. It is fundamental that the ability to utilize new forms in a custom module is added ASAP.

NicolePereira · ‎Apr 2, 2025

Currently, we make a form for every language we support. For us this means we will have 7 versions of the same form just for localization. Then we need to combine reporting and duplicate workflows and manage all these forms on localized pages. We'd like to have multi-language variants of a form with the ability to assign multiple sub-languages to a form, and the right form displays automatically based on the selected language. This could be a great enhancement to localization heavy HubSpot customers.

ChrisK_Avidly · ‎May 22, 2025

Currently for language variants of pages in Content Staging we need to create them as separate pages, set the language, publish and then attach them together as variants within Website pages. This is very cumbersome and for big sites, very time consuming. The language variant process and setup within Website Pages should be mirrored within Content Staging.

NicolePereira · ‎Apr 2, 2025

Currently, staging does not allow us to make multi-language variants causing us to move to production first then make all our variants on a default system domain, and then switch it to the live domain. If we could just get our full language page groups ready in staging we could publish to live and improve the development workflow.

NicolePereira · ‎Apr 2, 2025

We have a website where we group 22 language variants under the en-US primary page. But there are technically multiple primary languages. So having the ability to make subgroups of languages would help tap into the fallback language options. The primary language for a group becomes the fallback for all languages. If you land on a page missing that language then it will go to the primary. But we may have several languages that are associated and we'd like to select a primary for that group. For example: fr-FR (primary for this set of language regions) fr-BE fr-CH So if fr-CH is missing, Id like it to fallback to fr-FR but still have it in the larger associated group of language page variants.

Jake_Lett · ‎May 8, 2025

Lets say you build a dev site and have a 100 pages. By default it uses a domain like hssites-xxxx.com. Once you change your primary domain the page URL's update but the files used on each page still use the old domain. So you go and update the default file URL domain to your new primary domain. You assume this updates on all pages and your sitemap.xml... because you want it to be the default. But this only works for any future updates you make and publish. All of the pages you created using the temporary domain are not updated. So in order to fix this, you need to open all 100 pages and then republish them. "ain't nobody got time for that" : ) Could you please add a way to click a checkbox that says "Update all pages and sitemap.xml with this new file domain". Thank you.

Jake_Lett · ‎May 9, 2025

Could you please add the option to add a job title to a blog author. Or better yet, make this an object that we can create custom properties for. https://knowledge.hubspot.com/blog/create-and-manage-your-blog-authors

karstenkoehler · ‎Jan 24, 2023

Hello product team, For HubSpot admins, one of the biggest challenges is keeping a portal organized, cleaned up and prevent overall chaos. Especially in Enterprise portals with sometimes hundreds of users, it's almost impossible to get users to follow a naming convention for email names, landing page names, workflow names. Quickly this becomes a cat and mouse game where HubSpot have to constantly chase and remind users to name their assets correctly. Why is this currently a bad user experience for users? Naming conventions are usually documented outside of HubSpot, in a wiki, stored as a Google Doc or something similar along the same lines. Forcing them to interrupt what they're currently doing, look up a naming convention and then come back means that they're losing time. They also have to leave HubSpot momentarily. Even then, they might misunderstand the naming convention and type in an incorrect name. Why is this currently a bad user experience for admins? Incorrect naming means that list or workflow filters for Recent conversion might not work. It can also mean that reports become a mess, if these reports are pulling in asset names. If admins have to look into this on a permanent basis, in portals where there are new assets every day, this takes time away from developing the HubSpot portal and generating more value for all users. Here's what a solution could look like To solve this, it would be great if there were tools to enforce a naming convention. Ideally, admins would specify what constitutes a correctly named asset and similar to the forms editor, arrange fields to their liking. Here's a quick mockup of what this could look like when creating a new page. The user could select from dropdowns which team they belong to, the language of the assets, the asset type, include a title and date. The system would then generate a title from this that cannot be further edited. Admins should be able to specify the options for each dropdown, separators, order and field validation (e.g. max length for a title). (In case this is eventually introduced, please consider to make this a feature that is at least included in all Professional and Enterprise subscriptions.) I would love to see this for all assets in HubSpot: emails, workflows, lists, campaigns, imports, properties, files etc. Thanks in advance for reviewing!

NFricano · ‎Nov 20, 2024

Hi HubSpot Community, I'm writing to share some thoughts and suggestions regarding the new Case Study Beta feature. While it's a fantastic step forward, there are a few areas where I believe it could be further improved to provide users with even more flexibility and customization options. Current Limitations: Limited Listing Page Customization: The current listing page customization options, particularly around tag filtering, feel somewhat restrictive. Being able to create more granular filters and sorting options would significantly enhance the user experience and meet more business needs. Lack of Child Theme: The inability to create a child theme specifically for case studies limits our ability to fully align the design with the rest of our website. No Multilingual Variations: As with HubSpot's blog feature, the ability to create multilingual variations of case studies would be invaluable for global businesses. Header and Footer Customization: While there are some options for customizing the header and footer, they are quite limited. This often leads to design inconsistencies across the website, as the header and footer don't match the overall site design. Proposed Enhancements: Expand Listing Page Customization: Allow for more granular tag filtering and sorting options. (e.g., filter by solution and case study type; sort by date, popularity or custom field) Provide additional layout options for the listing page. (e.g., grid view or card view) Introduce a Child Theme Option: Enable users to create custom child themes for case studies, allowing for greater design flexibility and alignment with the overall website. (e.g. customize sections, fonts, and add new modules) Support for Multilingual Variations: Implement a similar system to the blog feature, allowing users to create different language versions of their case studies. (e.g. create a Italian version of a case study targeting the Italian market) Enhance Header and Footer Customization: Provide more flexibility in customizing the header and footer, including the ability to use custom CSS. (e.g. have more styling options for the menu items) I believe that by addressing these limitations, HubSpot can create a truly powerful and customizable case study tool. What are your thoughts on these suggestions? Are there any other features you'd like to see added to the Case Study Beta?

Great minds think alike

Roll back of opening multiple webpages in tabs

Allow for new forms to be used in custom modules

Allow forms to have multi-language variants

Allow language variant groups within Content Staging

Allow multi-language variations to be made in content staging

Create multi-language subgroups on pages

Changing default file URL domain should update all pages and sitemap.xml

Add Job Title Field to blog author

Enforce naming convention for new assets

Case Studies Beta proposed enhancements

Recently delivered

Recently in beta