Gute Ideen sollten geteilt werden

It would be very beneficial to have an edit footer option in the design manager templates. Right now when you add JS to the bottom of the template (either in a custom HTML or HubL Module) it adds the content above the both the following JS lines. <script type="text/javascript" src="https://static.hsstatic.net/content_shared_assets/static-1.4040/js/public_common.js"></script> <script src="//static.hsstatic.net/slick/static-1.30/bundles/project.js"></script> This makes it hard for us to customize things like the Gallery slider. In order to add customizations (from Slick Slider) we have to do it from the "Edit footer" area in the page settings (as this code get placed below the JS files above).  ... Mehr anzeigen

We want to see who in our database we aren't sending content to, so being able to easily generate a list of contacts who are not currently in any sort of workflow would be nice :). ... Mehr anzeigen

It would be great to have an automatic buffer time between meetings, ideally 15 minutes.  The issue on my end has been getting booked back-to-back for short meetings.  If I have three 15 minute meetings back-to-back and either of the first start late or run late it would throw my whole schedule off, (a domino effect of lateness).     ... Mehr anzeigen

One of the best features is being removed. The Chrome plugin saves my team so much time. Of course, you'd get rid of it. Seriously the most disappointing Hubspot news I've heard. Waiting for my sales team to freak out.  Here's the explanation my sales rep got when it wasn't working. "Although this is a feature that the team is working to remove from all profiles, and it's possible that they are making those changes soon. I'm not sure when this option will no longer be available." ... Mehr anzeigen

Today when we put one of our clients' HubSpot blog through the website grader, we saw that the blog had a page size of 13mb. The problem was that the images they we're uploading as the featured image were large images (3000x3000px+). We quickly figured out that we could resize the original image by adding and specifying a width attribute to the <img> tag. This process changed the page size from 13mb to 1.8mb.   I have two examples here: http://cdn2.hubspot.net/hub/53/file-733888619-jpg/assets/hubspot.com/about/management/brian-home.jpg?width=300 http://cdn2.hubspot.net/hub/53/file-733888619-jpg/assets/hubspot.com/about/management/brian-home.jpg?width=500 The first one resizes (crops) the image to a 300px width, and the second image it's resized (cropped) to a 500px width.   I got this back from support:  "looked into this and it does have to do with the url structure and our ability to intercept the request before our content delivery network receives it. With how these tokens grab the url of an image, we can not manually resize them.   Using the default CDN host, http://cdn2.hubspot.net/hubfs/53/00-Blog_Thinkstock_Images/hubspot-15k.png?width=761 needs to be changed to http://cdn2.hubspot.net/hub/53/hubfs/00-Blog_Thinkstock_Images/hubspot-15k.png?width=761"   Because we are using the featured image tag, {{ content.post_list_summary_featured_image }}, we can't edit the URL to include the "/hub/"-part. Is it possible to implement that on the featured image url as a standard so we can specify the width in the url on future blogs? ... Mehr anzeigen

Our team uses TeamWork PM for all of our project management and task tracking.  The hubspot task option doesn't notify me and the emails get caught in my 'promotions' tab of the email and go unnoticed.  It would be great if hubspot integrated with TeamWork so that when i create a task in hubspot CRM it created one in TW for me under a sales project. ... Mehr anzeigen

Migrated from legacy feedback forum with 68 votes.   I have had several instances where the ability to set the default values for form fields would have saved me hours of integration time.   For example: My client has 10 webinar pages each with its own unique thank you page. Our current form configuration (not-HubSpot integrated) redirects the user to the appropriate thank you page which contains the webinar requested for view.   I can already dynamically change the thank you page destination from the form embed code - but what I am looking for is to also set a hidden fields value inside the embed code as well.   For example the embed code would look something like this: <script> hbspt.forms.create({ portalId: 'XXXXXX', formId: 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX', formFields: { fieldID1 : { value : "my value" }, fieldID2 : { value : "my value" } } }); </script>   Where the field ID parameters and their values would correspond to certain fields (hidden or visible) in the form. This would allow me to use a single form across multiple pages on my site and also be able to send through the correct values for certain form fields based on the action / content they requested on the site.   If you guys can do this - or if it is already possible and I didn't know about it - I would love you forever. ... Mehr anzeigen

One of the biggest oversights in the COS is that it's very difficult to create looped content. As far as I'm aware, the only thing that lets you do a loop is a slider (if you use export_to_template_context), which has a limited number of fields per iteration. Consider this simple case: I want to create a custom widget where the user can create an arbitrary number of buttons. Each button has a link, text, and a few style options. Currently , they way I would have to do that is to decide what the most buttons I would ever need is, then add that number of each field (for example, five links, five button texts, five style drop-downs, and then distinct markup for all five). Obviously, a very tedious process. And if I want six for some reason, I have to go back and edit the module. So, here's how I envision this working. First, add a new option to the custom widget editor to create "field groups". Field groups could contain any number of other fields (perhaps even their own child field groups, because why not?), and would have their own labels, names, and description fields. Then, the person using the page editor would be presented with those fields grouped together visually, with add and remove buttons. Clicking add would create a fresh copy of all the fields in the group, clicking remove would remove that item in the group. Then, in the template, you would have the ability to iterate through items in the group with a for loop. Something like this: {% for button in widget.field_group_name %} <a href="{{ button.link }}" class="{{ button.style }}">{{ button.text }}</a> {% endfor %} The user can have as many buttons as they please, the page editor doesn't get clogged with useless fields, and the code remains simple and easy to maintain. This would give developers a lot of control over presentation without sacrificing ease of use for the page editor. I really can't emphasize enough how much this would simplify certain aspects of template building. ... Mehr anzeigen

When creating templates in design manager, particularly CSS templates, it would be useful to be able to generate a dynamic URL for this, similar to the way URLs are used in File Manager.   If you are integrating a third-party plugin, such as an iframe on your Hubspot hosted page, and you need to reference a stylesheet in the source code of that iFrame via the third party website, you could just grab the URL of your hubspot css template and link it in the source.   So for example, you are placing an iframe for a job hosting board on your site, and you want to be able to style that iframe using your "main-theme.css" template as the linked stylesheet. The job hosting service could place in their source code the URL to your design manager template "main-theme.css".   This way, you could edit the css file in template builder, then refresh your page, and see the changes immediately, without having to re-upload a css file to file manager. ... Mehr anzeigen