Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • The edit game feature needs some serious attention. It doesn’t work really.

    Thread Starter proturnkeys

    (@proturnkeys)

    I have since been told that the error was caused by the custom sidebars plugin, not Widget Options, but it also seems that the visibility feature of Widget Options does not work with Pagebuilder, according to the following notice:

    SiteOrigin Pagebuilder Support

    This feature will enable the widget options to your widgets when you are using Pagebuilder by SiteOrigin. Easily manage and extends widget functionalities and visibility using tabbed options provided for each widgets.

    Limitations

    – Visibility options tab option is not available since you are using pagebuilder.

    – Custom widget ID on pagebuilder widget was removed to avoid conflicts.

    That’s all! Other options will work smoothly and integrated perfectly on the plugin.

    No additional settings available.

    So it seems I cannot find a visibility plugin to work with pagebuilder, which is a big problem on my site. Although I haven’t tried Jetpack yet. Very reluctant to install that.

    Regards
    Matt

    • This reply was modified 7 years, 4 months ago by proturnkeys.
    • This reply was modified 7 years, 4 months ago by proturnkeys.
    • This reply was modified 7 years, 4 months ago by proturnkeys.
    Thread Starter proturnkeys

    (@proturnkeys)

    Hi,

    I haven’t tried cloudflare yet with subdomains. Thats an interesting feature they have. Paid plan or free?

    Really appreciate you looking into a fix for X theme and CDN enabler. There seems to be thousands of people using X theme, its very popular so its probably worth it.

    I check back in a few days ??

    Regards
    Matt

    Thread Starter proturnkeys

    (@proturnkeys)

    HI,

    I took away that exclusion and this time I could access the skeleton,but not the proper interface. Still, getting rid of the exclusion took off another 4 requests.

    The url is always https://example.com/x/
    If you are editing a file, like say the home page, it will be something like https://example.com/x/#/content/34

    Have a chat to theme.co for further information. I have seen one or two posts for support requests on their site regarding compatibility between their theme framework and FVM.

    Cloudflare is excellent. Only problem with them though is that to take true advantage of everything you need to use their DNS. This site im working on is testing DNS Made Easy, which is a premium DNS service and I must say it certainly beats my domain registrar. Big reduction in initial lookup time etc. Also this particular site will be using push zones, so I will be hosting big files on CDN for customers to download.

    None of those 6 urls I outlined are written to the CDN. They all appear from the origin server, but my CSS and PNG files come from the CDN.

    If I disable your plugin, the CDN picks up what is now at least 26 js files successfully. My http requests go from 16 to 52 and page load time increases by as much as a second. Its nasty. I do like your plugin, it does wonders and it doesnt seem to conflict with W3 Total Cache, unlike say Autoptimize which has done in the past for me.

    I am using Cloudways for my hosting on a Vultr plan so I would be using all the caching and performance features their plans come with. That might also be causing a problem?

    Regards
    Matt

    • This reply was modified 7 years, 6 months ago by proturnkeys.
    Thread Starter proturnkeys

    (@proturnkeys)

    Hi,

    Unfortunately I have to keep those exclusions because without it, when I attempt to accesss X, which is they’re page layout app (similar to Visual Composer for WP) it never loads. It basically just goes into an endless loop and shuts down WP admin completely from access. With those exclusions I can at least access X in “skeleton mode”, which gives me the functionality without the pleasant eye candy.

    In terms of the CDN plugin, i tried both CDN Enabler and the CDN section of W3 Total Cache.

    None of the URLs are being written to the CDN, they are still being pulled from the origin server, so https://mysite.com rather than https://cdn.mysite.com

    I thought it might be a headers issue, but maybe, if they are not being picked up at all, its something else?

    Regards
    Matt

Viewing 5 replies - 1 through 5 (of 5 total)