วีดีโอ

my wf_sif cookie is blocking my login functionality via memberstack

Unfortunately not, it's an Httponly cookie which means it can only be accessed by the server, not JS.

@@jordancornelius1433 I'm not certain what that cookie is, it doesn't show for me on a standard login. In any case I would not expect it to affect memberstack in any way- MS has it's own independent set of cookies. I'd contact Memberstack support if you're experiencing a conflict.

@@sygnaltechnology773 Thank you for the reply. I realized it is easier to link memberstack events to the default webflow systems rather than vice versa. thank you.

If you mean the ability to enter the current timestamp quickly, I use AutoHotkey ( AHK ) for that and bind CTRL+; ( semicolon ) so that I can create timestamps in any program, anytime. That hotkey is already used in Google Sheets for timestamp entry, so it's a consistent way to drop timestamps in Google Docs, Webflow, etc.

Display: none only affects visibility so it comes down to the size of the content you're hiding. Ideally you only want you page to contain content that benefits your users, so if you're planning to show it later ( tabs, sliders, multi-step forms... ), it's generally ok in moderation. If half your page will never be seen, it's probably worth rethinking your design approach.

@@sygnaltechnology773 i have some fotos and videos in a slider, but that fits not good in my mobile, so i will (display none) the slide in mobile and show a grid with the same content as in the slider, so i have have doubled my content, because the grid is on display none above mobile but it still exists, thats not good, but my idea is that i make every image and video to an component, so it have to load only once, could that work?

@@private_krapfen950 No you'd still likely use 2 instances of that component. You could solve this with JS, but realistically the approach you're using ( desktop version, mobile version, hide-and-show ) is pretty standard and fits Webflow's designer paradigm better. I wouldn't sweat it. If you're using the same image assets, the browser will only load them once and that's going to be the bulk of that content.

Did it?

Glad it helped!

I believe it should be possible now through the API, but would require some careful work to manage the rate limits as most sites have quite a few assets. Also it would likely only get the asset folder and nothing stored in the CMS. developers.webflow.com/reference/get-asset

Last I checked you can add markers, including pop-up information - but you cannot highlight regions. It's likely you can do that using the Google API directly but will require programming. Check Google's Javascript Maps API

Thanks Ben I really appreciate it.

They are completely unrelated. Webflow is pretty consistent in that thing under Settings have nothing to do with CSS, which is all under the Style tab. The naming similarity to the visibility CSS property is unfortunate, but maybe unavoidable.

Hi Komasator, you need to unbind it from the CMS to style it. In general, I create an RTE with the same class on a drafted style guide page which I use for styling. It contains all of the elements I'd use in the CMS content- list items, blockquotes, headings, etc. This makes styling easier.

Yes it works fine, we still use this more often than we should need to. Watch the video closely especially the part where the style overrides are applied, I recall there's a trick to getting the webflow designer to accept a style override when it thinks it's unchanged.

This approach does not, but there are quite a few other approaches; www.sygnal.com/courses/webflow-tables

@@sygnaltechnology773 thanks so much!

The primarily point of vis hidden was to support conditional vis on login state, and soon localization. But it's just as useful with no conditions, since it's the only way to exclude page content from the DOM without deleting it outright. We've also used components for this in the past, however that can create hundreds of components, and loses position information. For a client, managing their site, that's a pain. An example here is the covid banner notices & pop-ups. They were part of many client site-navs as a component within a component. Having to remove and re-add that was too complex for many clients, so we built intricate CMS-driven banners and popups. Overkill. Here, they just click visible/hidden, publish and done. Happier design team, and happier clients.

@@sygnaltechnology773 I guess we agree to disagree : )

@@fathom5209 Absolutely, but I encourage you to use the tools in the way they most benefit you. We're currently doing a bunch of site redesigns and template grafts onto existing sites and this one little feature has been a gamechanger.

Hi Dennis, RTE's connect only to CMS rich text fields, you can't connect them to plain text fields. Check your field types when you encounter this problem. Also make sure your RTE is actually in a CMS bindable context, such as inside of a collection list or on a collection page.

Hi Aurora, unfortunately I have no experience with Wix, or what embedding options it offers. I'd check first to make sure that it's actually generating the right code in your published HTML page. Also make sure you publish first, most platforms won't show embedded code while you're in the designer environment ( because it can interfere ). If you're seeing the code properly, than it's something to do with your API key. Perhaps it needs to be configured for maps, or given permission on the right domain names for access. Google docs will help you there.

Yes, they snuck that EMBED-in-richtext widget rather quietly, I first noticed it about a year ago. Handy little feature though, for handling those edge cases where you need to display something that doesn't fit into the regular richtext element types. Thanks for reminding me of this, I'd been wanting to expand this and add it to Webflow Utils.

I'm not sure of the limit but what you're describing sounds more suitable for a dynamic map, fed from a CMS collection. You'd have a lot more control that way.

In fact, text inside of images is part of your SEO. However I'd personally prefer HTML content if SEO was a critical factor. For more on Google's OCR capabilities look here. cognitiveseo.com/blog/5909/did-google-read-text-image-can-affect-my-rankings/

In our experience multiple blocks are fine, so you can embed the JSON+LD output directly into eg an events collection you're emitting into the page.