Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter mike_freegan

    (@mike_freegan)

    It was server side. SOmething wrong with SQL performance. Hosting provider had to resolve it.

    Thread Starter mike_freegan

    (@mike_freegan)

    I am the theme author.

    I’ve solved this anyway. It was Adblock Plus for Android. Lesson: don’t use the word ‘adverts’ in your page URLs or they will get caught by AdBlock.

    Thread Starter mike_freegan

    (@mike_freegan)

    Hi Andrew

    I’m just using the Chrome dev tools with a couple of extensions.

    Yes, I could see that main.js was being called, but had no idea what was calling it. I assumed it was a WordPress thing or something put there by one of my many, many plugins.

    Turns out it is a placeholder I’d left in my footer when I started building this theme weeks ago to remind me to include scripts there. Derp.

    Thread Starter mike_freegan

    (@mike_freegan)

    Hi Andrew

    That did it, thanks. It is actually my own theme, but I am admittedly quite new to this.

    What is main.js? Is this something that I should always include in a theme?

    I wonder why it has never caused issues before.

    Hi

    Late to the party, but I’ll answer in case anyone else comes across this.

    In my case, custom post fields just wouldn’t calculate. I presume this is a bug with Gravity Forms.

    Anyway, I found a way around it. First, set up your custom post field with the calculation in. This won’t work. However, you then need to make an additional plain old number field (not linked to a custom field) with the same formula in, and use the same field label as you use for your custom field

    Somehow it makes them both work. Just hide the one you don’t want visible by making them available to admin only (under the advanced tab in the field settings.)

    EDIT: You can hide your custom post field, but if you hide the plain number field, the value doesn’t get passed to your custom post.

    Thread Starter mike_freegan

    (@mike_freegan)

    Well, I didn’t think it would be a plugin because it was affecting the image even when I tried to access directly. BUT I de-activated all of my plugins which fixed it.

    Then I went through one-by one, and it works fine with all of them re-activated.

    And this is the version of WordPress that was current when the site launched in September.

    Thanks for your help!

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