Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter timendres

    (@timendres)

    Indeed!
    I cannot understand why Google would make that change.
    Somewhat confusing to be honest.

    Thank you very much for pointing this out.
    The new key has resolved the problem.

    Thread Starter timendres

    (@timendres)

    Hi Michael,

    As a website development firm, we are engaged in developing at least 3 websites simultaneously all the time. We make very extensive use of custom posts, and typically complex posts. So we were engaged with the plugin frequently on a daily basis.

    Thread Starter timendres

    (@timendres)

    Hi Brad,

    My apologies for the “dumb” comment. I often forget I am not in the company of those who are familiar with my (sometimes poorly chosen) humor and incessant movie references. You guys are clearly not dumb, and your excellent plugin, which is a rare gem, proves this. My bad.

    I was just extremely disappointed that I had to drop a plugin I so relied upon.

    I am not trying to get support here, as I have moved on and no longer use the plugin. Just attempting to alert others to the issue in case it is vital to them. Yes, my location has internet issues at times, and being located outside the US, latency adds up. That said, there is no reason why you cannot cache all of the relevant information and eliminate the issue entirely.

    Regards – tim

    Thread Starter timendres

    (@timendres)

    Hello Michael,

    Thank you for your reply.

    I did not mean to imply the problem existed for every page load in the WordPress backend. But it does exist for every page load of the CPT UI plugin. And that makes your plugin literally unusable for me. I cannot wait 30+ seconds for every page load while I am creating and editing my custom posts.

    After looking at your code, I can see it is not the plugin hitting your server for that JSON data that is the issue. It is the three requests to show get the images that the JSON data points to:

    [
    {
    url: "https://pluginize.com/product/custom-post-type-ui-extended/?utm_source=sidebar-v3&utm_medium=banner&utm_campaign=cptui",
    image: "https://rvyfxo7o23yu7s65vok119jt-wpengine.netdna-ssl.com/wp-content/uploads/2016/05/cptuix-ad-3.png",
    text: "Custom Post Type UI Extended product ad"
    },
    {
    url: "https://apppresser.com/?utm_source=pluginize&utm_medium=plugin&utm_campaign=cptui",
    image: "https://rvyfxo7o23yu7s65vok119jt-wpengine.netdna-ssl.com/wp-content/uploads/2016/05/apppresser.png",
    text: "AppPresser product ad"
    },
    {
    url: "https://maintainn.com/?utm_source=Pluginize&utm_medium=Plugin-Sidebar&utm_campaign=CPTUI",
    image: "https://rvyfxo7o23yu7s65vok119jt-wpengine.netdna-ssl.com/wp-content/uploads/2016/05/maintainn.png",
    text: "Maintainn product ad"
    }
    ]

    There’s the problem. That explains the 30+ seconds to refresh the page.

    The only way you are going to fix the problem is to cache those images when you cache the JSON data. Waiting for that once per day is acceptable.

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