Help us improve

Tell us how we could make the product more useful to you.

When updating CRM user's email optionally allow form case emails to be updated.

If a website visitor uses an incorrect email in a form submission a new entry is created in Users & a form case created & attached to this new user. Agency/client can update the CRM user but the form case still has the incorrect email (unless fixed via an import). Would be great to have functionality added to CRM to allow all form cases with incorrect email to also be updated to the new email. Use Cases: This allows for ecommerce invoices with incorrect email to be fixed & invoice/receipt to be resent easily to purchaser. Member/ecommerce websites frequently have this issue where a member accidentally uses one of their other emails to purchase/submit a form outside of the secure zone. The transaction is then not in their list of purchases/form submissions.

Liz Gibbs 11 days ago

πŸ—οΈ

Improvement

In Progress

Meta Name="robots"

I believe I am correct in thinking that the Siteglide system doesn’t include a meta name=”robots’ tag if in the page editor the page is set to β€˜visible to search engines=Y’. If this value is set to N, the tag is inserted within the section as but that is not always what is wanted (see 2 below). 1. I believe all web pages should include the meta robots tag regardless; and 2. there are occasions when an SEO company might want to stop SEs indexing a page, but not stop the spider crawling and following the links within. In this scenario, the only way to edit this is to make the page visible to SEs and then use liquid in the template to say:- if the page URL = β€œxxxxx” rewrite the tag to β€œnoindex,follow”. It would be a massive improvement to be able to edit the meta robots tag from within Site Admin/ page editor. Please!

Robert Wakefield About 1 month ago

2
πŸš€

Feature

In Progress

Pages - Custom Fields

Page metadata can support nested info, and therefore would be fantastic to have structured data in pages, which would allow clients to easily edit content in a safe CMS based environment without having to go in the visual editor or code, which has caused clients to break layouts in the past, which normally leads us to recommend to clients to not touch pages unless they know what they're doing. As a solution to this, we have often created Webapps with a single item in for the client to mange. Not only does this clutter up Webapps, but it takes the data out of context, and if not properly maintained, can cause fields to be redundant and not used as the site is updated. Structure like this would be fantastic: https://gist.github.com/JoshCarterWeb/32ecb3174ca367ac8ba5360293d5997b It would also be a mega bonus to not have the fields named customfield2. It makes things so much harder.

Josh Carter 6 months ago

9
πŸš€

Feature