Forum Replies Created

Viewing 15 replies - 31 through 45 (of 95 total)
  • Thread Starter Melpomene

    (@melpomene)

    Difference between .com and .org

    Resolved (well at least in my understanding)

    Thread Starter Melpomene

    (@melpomene)

    I used it previously and had issues with it so switched to the one that’s broken and which we must assume by now, isn’t going to be mended. Sadly I can’t remember what the issues were, so perhaps I’ll give it another go

    Thread Starter Melpomene

    (@melpomene)

    I’m tempted to ask what a Masterlist is? That must be the first time I’ve ever had anything put on it! I might be raises sensible enquiries at last!

    I think the upshot is that the plug-in is the culprit. I did the same as the rest of you, and loaded the images without any problems.

    With the plug in disabled though the site will display the HTML behind it in a block. The answer seems to be to try and work as quickly as you can with the images and then reinstall the plug in to regain the maps

    I guess the author will put this right pretty quickly though? He seems to be quite active and helpful in the plug in section

    Thread Starter Melpomene

    (@melpomene)

    To be honest Andrew, I think the diagnosis might be moving faster by having a number of people jumping in on the existing one as it’s clearly a problem a few of us having and the link MCG posted seems to indicate that it’s only really become known about in the last few hours (not that the explanation in that links means anything). It sounds as if the plug in author needs to do something doesn’t it

    Thread Starter Melpomene

    (@melpomene)

    Thanks for the reply TechNinj, as it is worth folks like myself with very limited knowledge being aware of these things, but since it’s the one button, and one function that seems to be effected I’m not sure your description fits. Also the fact that MCG has restored functionality by disabling one of the plug-ins we’re both running, it seems to indicate that Comprehensive Google Maps Plugin isn’t competiable with WordPress 4.0 I think (or that would be my take on this)

    Thread Starter Melpomene

    (@melpomene)

    Haven’t dared to look at widgets yet WDT

    Thread Starter Melpomene

    (@melpomene)

    Akismet and Google maps Plug in I’m running too

    Akismet is widely used, if there was a conflict it would be known I’d assume. My best guess is the maps are the most likely culprit

    I did run Jetpack until 30 mins ago! decativated hoping that was responsible as its pretty useless and I could run without it. But it wasn’t. Then it wouldn’t let me reactivate without password and user names!!! bloody useless like I said

    Thread Starter Melpomene

    (@melpomene)

    That sounds plausible, but I checked another site on the same theme that hasn’t been the subject of the dreaded auto update to 4.0 and there wasn’t a button there, so I’m inclined to think it could have been a figment of my imagination. I just sensed there used to be button there I never used as contact form were done through the plug in contact form 7

    Thread Starter Melpomene

    (@melpomene)

    What plug ins are you running MCG?

    I’m guessing that must be the culprit as I can’t believe that WordPress have built a so called upgrade and disabled their ‘add media’ function. I mean it’s a pretty basic thing.

    I’m guessing that between us we must have something similar if you’ve got the problem across different themes. I’m only running the single Woo Commerce theme, but my understanding was that they work closely with WordPress and tend to come from off the same page

    Thread Starter Melpomene

    (@melpomene)

    Right the missing button is a figment of my imagination. The contact form still works. It’s just the ‘add media’ button that’s failing. I don’t know what describe it as? It’s just dead. You click on it, and nothing happens

    Thread Starter Melpomene

    (@melpomene)

    Thanks Evan,

    Strictly speaking its a commercial site, (I should have made that clear really) even though it’s in hibernation, but I’m sure if I asked Akismet to protect it they’d realise it’s a dot.com.

    I wouldn’t want to do something dishonest like that really as I don’t think we can take the high moral ground against the abusers if we start doing things like that. Admittedly $5 isn’t much and there are bound to be those who simply say pay it and stop being so tight fisted, (I understand that) but there’s also this silly thing gnawing away at me that says why pay anything for something that it isn’t actually active (so to speak) for however I look at it, it’s dead money for about 15 months. There’s also this bit of me that thinks that should be a solution in WordPress (like disabling comments) but clearly that doesn’t work.

    Am I reading this wrong Mark?

    “We’ve yanked the feature. I’ve just released Wordfence 5.0.3 and the only difference is that we’ve completely removed the ability to disable XML-RPC.”

    Surely it was the fact that we could to disable XML-RPC that allowed us to install the update (Woo in my case, as I operate a Woo theme). If your update removes this capacity, won’t the issue return?

    Could be totally unrelated of course, so be wary of any advice I give out, as I’d be a long way from knowledgable. All I know is my own update wouldn’t install until I performed this, although I got a series of different error messages and hadn’t hit the issues you’ve got. Mind you, if you aren’t running Wordfence you can safely discount my answer

    Same thing happened to me

    Are you running Wordfence?

    If you are it’s likely to be the problem as there’s a bug in it.

    Click on the Wordfence plug in thing in the left hand side menu of your dashboard

    Go to ‘Options’ at the bottom, then scroll down to ‘other options’ uncheck the box ‘Disable XML-RPC for DDoS protection’ and save changes. It installed after that

    Actually on reflection, it wasn’t necessary to include the quote from my hosting company, and I don’t see that it adds anything to the above post other than to provoke.

    The observation that the Woo Commerce plug in is affected however is valid, as seems to be the instruction for resolving (in my case) but if someone could remove the unecessary quoted bit that serves no useful purpose I’d be grateful (I have tried to find a moderator contact but have so far failed)

    Thanks

Viewing 15 replies - 31 through 45 (of 95 total)