Forum Replies Created

  • I use tabs a lot too, and I was thinking that we could take advantage of them to load assets (scripts, field images etc) in a smarter way. For example, when the post edit screen opens, it would only load the js and images of the fields that exist under the first tab. If the other tabs contain fields with extra scripts and images (for example Google Maps), then it would load them only when you click on the specific tabs.

    If the same could be done with db queries it would be perfect, but I imagine that this would be tricky. Scripts and images, on the other hand, sounds more feasible.

  • I know it’s too late for the topic starter but I had a similar issue today and I bumped to this post, so I thought it might help somebody else if I shared my solution. In my case it was caused because my theme’s folder had different owner (probably due to the fact that I uploaded the theme via ftp). As soon as I chown’d the correct permissions it worked.

  • I agree too that this should be a native functionality. Zoom level is an important piece of information for any map. Sometimes content editors get confused because they expect to see at the frontend the same zoom level that they chose at the backend.

    Personally, I would add an extra option “capture zoom” at the map field, disabled by default. If the website’s admin chooses to enable it, it would warn him/her that this would disable the “scroll to zoom” functionality.

    In fact, if it were my decision, I would prefer the “scroll to zoom” functionality disabled by default anyway, because of the accidental scrolling. Even if it currently doesn’t affect the output, the end-user doesn’t know it and sometimes tries to bring back the zoom level and position that he/she accidentally lost.

Viewing 3 posts - 1 through 3 (of 3 total)