Jump to content
ygirod

Chrome is required to use PageLines editor ?

Recommended Posts

ygirod    0
ygirod

Hi,

I tried to work under Firefox 22.0.

Message of DMS: "Chrome is required to use PageLines Editor"

Really ?

Share this post


Link to post
Share on other sites
tomchalky    0
tomchalky

Exactly what it says on the tin. Chrome is always 10 steps ahead of all other browsers.

Share this post


Link to post
Share on other sites
Rob    547
Rob

Hi,

 

Chrome is only required for the visual editor and for the design/layout/styling of your site.

 

When adding posts or pages or any content to WordPress, you can use any browser.  Unfortunately, at present, only Chrome provided the tools and resources needed to make our visual editor possible.  As time progresses, others will upgrade their systems and probably catch up to where Chrome is now.

 

Please see our Docs for further information.  http://docs.pagelines.com


Former PageLines Moderator, Food Expert and Raconteur

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

    • Michael Kummer
      By Michael Kummer+
      Hi guys,
      every since Chrome introduce scroll anchoring (see chrome://flags) blog posts on my page start scroll automatically as soon as the user scrolls down a bit. It is super annoying and I don't know exactly what triggers the incompatibility with Chrome's latest feature that is supposed to improve usability.
      Since I don't know what causes it (Pagelines, or a Plugin), I would like to disable the feature using a CSS override that Google describes as follow:
      "Scroll anchoring aims to be the default mode of behavior when launched, so that users benefit from it even on legacy content. A CSS property overflow-anchor can disable scroll anchoring in part or all of a webpage (opt out), or exclude portions of the DOM from the anchor node selection algorithm. This property supports the following values when applied to an element E:
      overflow-anchor: auto (the default value) declares that the DOM subtree rooted at E is eligible to participate in the anchor node selection algorithm for any scrolling box created by E or an ancestor of E. overflow-anchor: none declares that the DOM subtree rooted at E is not eligible to participate in the anchor node selection algorithm for any scrolling box created by E or an ancestor of E." Do you guys happen to know how to use that property with the ROOT element so it applies to the whole page?
      Thanks
      Michael 
    • jagipson
      By jagipson+
      We had this site on our cloud 9 server and moved it to a Amazon Web Service server using Cloud Front and now the Editor on chrome is missing just says USE GOOGLE CHROME TO EDIT WITH DMS. Have tried multiple computers and same results. Any solutions why we would be have this problem?  Won't work on any page.
      http://www.viaglobalgroup.com/
      Thanks
       
      Matt
      @Danny @Andrew 

    • bnapoli
      By bnapoli+
      On my site www.modishmel.com I'm seeing the "blog post title" within the "pins" plugin section breaking words into multiple lines. See screenshot attached.
      Only seeing it in Firefox. Can you help?

    • abuzzelli
      By abuzzelli+
      Strange issue popped up...this site's header http://pattimhall.com looks right in all browsers except firefox. This is what it should look like:
      https://drive.google.com/file/d/0B49uWjV65L5RTGdHSFdsbzBDbTg/view?usp=sharing
      This is what it looks like instead:
      https://drive.google.com/file/d/0B49uWjV65L5RVTVLbnA5aUowWDQ/view?usp=sharing
      Any idea what's going on here?
    • richardjacruz
      By richardjacruz+
      I noticed that the cached version of the website from a Google SERP has broken CSS:
      http://webcache.googleusercontent.com/search?q=cache%3A1uyPM2gXGG0J%3Astevensoncrane.com%2F+&cd=16&hl=en&ct=clnk&gl=us
      Any idea why? The site looks fine elsewhere.
      Also, when using the Web Developer Toolbar in Mozilla Firefox, there are a BUNCH of warnings regarding CSS. I'm wondering that's the problem with the Google cache.
      In a prior post, I had experienced similar "breaking" of the CSS, but that was due to some errors in DNS. I thought we resolved all of that, so this perplexes me.
      Thanks,
      Rich
×