gazouteast

Get back under your bridge with the rest of the trolls

Whooami – I now believe you are that arrogant schmuck known as Richard Ambrose – if not then you must have been cloned from the same cell in the same test tube.

Since when did you become the registrar and domain keeper of all my websites?

Note what you quoted –

“I have several blogs that cannot ….”
– since when does “several” mean “absolutely everything”?

“I have basically stopped upgrading past 2.6.5 because ….”
– and as you know from your trolling of my other posts – I do have a number of blogs running 2.7.1 – hence participation in this thread.

” … on all hosts we use, on all continents … “
– oh dear – should I have qualified that with the trailing clause ” … that we use”? Is English not your first language then? Are you unable to identify the implied conditional addition to that sentence?

STOP BEING SUCH A NITPICKING TROLL AND FOCUS ON THE TECHNICAL ISSUE(S) REPORTED IN THE POSTS !!!!!!

whooami – your post is completely off-topic and irrelevant – stop being such an arrogant donkey.

Waves to v9 – appreciate another Thai-based user confirming what I’ve said in other threads about the appalling connection speeds here.

However, this issue is not the ISP’s fault (though they do contribute heavily to it) – it is most definitely a WordPress problem – we don’t get it with other scripts that we use on our sites – only with WordPress and only in the admin side – on all hosts we use, on all continents.

jd – thanks for that – I’ll have to revisit this over the weekend and have a play with a test install of an older version to see if I can get the hang of it.

As I said – anything that saves time will be a great help.

(but I still prefer SMF Forums’ upgrading system ?? )

Hi Sam

Why not just protect it? Because it is still there under the same name and protecting it causes the hackers to try and brute force it, leading to server load issues and suspended hosting accounts – far better to obfuscate and hide it (plus protect it) with a different name.

Yes – it now happens with ALL plugins on any of my non WP2.7.1 blogs

That is – all my WP 2.6.x blogs are having this same problem with ALL plugins on ALL hosts

Looks like something at the WP plugins directory has changed, such that 2.6.x WordPress installs are being forced to upgrade to 2.7.1 whether the site owner wants to or not – i.e. how the plugin packages are zipped appears to have changed (I could be wrong though).

This, if true, is highly unethical as not every plugin has been, or will be, upgraded for 2.7.x and above, and some sites rely on specific plugins that will have 2.6.x as their final WP version.

I’ve checked, and all my hosts are using PHP 5.x and MySQL 5.x so it doesn’t look like the issue that Lester Chan offered a hack-workaround for (plus the symptoms of what his hack fixed were different to this issue.

bump

Further checking on this reveals it is only happening on my WP 2.6.x blogs – but is happening on ALL the 2.6.x blogs, with ALL plugins – it is not happening on any of the 2.7.1 blogs

(Before anyone says it – I have several blogs which CANNOT be upgraded to 2.7.1 because of core site functionality derived from plugins that have not been, and will not be, upgraded for 2.7.x and beyond.

It is therefore looking like some change or other has been made in how the plugin repository is packing the plugins, which is causing the double folder name in the path …

… unless someone knows something I don’t ?

This post should be stickied to the top of the forums – I’ve seen countless posts about this very issue, and I’ve suffered from it myself for 2 months.

Just went and checked FireFox and it had self-deselected the 3rd-party cookie option at last upgrade

dohhh!!!!!!

My blog is self hosted

I have the same problem – I’ve even deleted and manually reinstalled the plugin – I’ve requested a new password several times and still get the same error when using each of the new passwords. The API key is correct.

This issue appears on all my blogs (a mix of WP 2.6 and 2.7.x

There are dozens of threads about this here in the wp.org forums – why will none of the developers address this with some serious concern?

Gaz

Hi – I use both Wynton and Brandford themes by those themes’ author – no problems at all.

If you see the theme author’s site, he has a mini-forum where you can get a list of the image field names for the different images that are used (e.g. home-category-image).

I suggest you create one featured post that uses every possible image field and create each of them in the custome fields section – wordpress will then remember them and they’ll be available for future posts without having to think about them.

Make a post-it note for the recommended sizes and stick it on your monitor, or hack the WP write page code and insert a text table of sizes and field names (it’d be nice if Michael actually created a plug-in to do that for each of his themes as they have so many different custom fields and max sizes – but that’s another argument)

Hope it helps
Gaz

I’ve had this same problem intermittently on one of my WP blogs – it began in v2.5 continued in 2.6.x and now in 2.7.x

I contacted the host when they were still on PHP 4.x and MySQL 4.x and they twiddled something – I presume in htaccess or in php.ini but wouldn’t tell me what they’d done. Each time it seemed to fix it for a while then it came back. Each time I upgraded WP it came back. (I never thought to check, but it’s possible it also returned after plug-in upgrades).

Now they’re on PHP 5.x and MySQL 5.x – it seems to have disappeared, but could be just the cumulative effect of all the twiddling and tweaking they did each time I reported it.

Sorry I can’t be of further help on this, other than to recommend using your hosts live support function every time it haoppens – and be sure to tell them exactly what you were doing, with which WP page URL, and the exact error messages you receive.

Gaz

Delete the whole re-install from the server after saving your wp-contents folder to your local system – also before deletion, download your wp-config file and wp-settings file from wp-admin

Virus scan etc your wp-content folder and clean as advised by your AV software (it might find nothing)

Compare the file dates of your wp-content folders’ files to those of your plug-ins, themes, and wp original files (the copies from before upload) – look for very recent file date and size changes – inspect those files for script injects.

When your wp-content folders and files are “clean” change your database and FTP logins and passwords

Re-upload WordPress
Upload your cleaned wp-config and wp-settings files back to admin

Copy up any files you customised (from your saved WP-content folders)
Copy up clean plugin and theme copies from your original downloads

Run the install, configure plugins and themes

Your database will still be there.

jdembowski & figaro – you’re both suffering from the blinkered “we live in a developed country with developed IT infrastructure so we’re OK” viewpoint.

I’m 12,000 miles from my hosting server, in a country where the internet collapses every time it rains or the wind gets above 10mph (overhead lines and inept telco technicians).

What starts at the exchange as 2MB broadband (fastest available in this country) reaches me at around 500K and regularly drops to 4K for extended periods, if the connection remains at all. Every time China or Singapore sneezes, this country loses all international internet for days. A few years back, we lost all international internet for nearly 3 months because a fishing boat dragged anchor in the South China Sea and broke THE (i.e. the only) cable.

Add to that a country supposedly on stable 220volts 50Hz with a main electrical supply that yoyos between 0v and 350v and you start to get an idea of what we’re facing here. Just because we have a connection now, does not mean we’ll have it in 2 seconds time.

This country is not exceptional – geographically, there’s more than 50% of the world in the same state.

figaro – 10-second upload for the WP zip? I wish – see above.
JD – SVN – what’s that then? And how do you use it?

Thanks to a wild and random thought, last upgrade I simply copied the entire WP install on the server to another folder as an “instant” and temporary back-up solution – seems to have done the trick in terms of cutting job time drastically, though I’m now at risk of having my hosting account suspended for using the hosting space as a file store.

Across hosting servers in several countries, I have many installs (not just one blog), and would welcome anything that drastically reduced upgrade admin (as well as back-up admin). Having also a portfolio of other ecommerce and community sites leaves me little time to do the required research and self-education (“can’t see the wood for the trees” syndrome).

I do still stand by earlier comments though – an automatic upgrade from 2.7.0 to 2.7.1 should be parsing the changes, not overwriting the whole directory structure. Even just a file by file XML would save the deletion of non-core directories and files – at a developer level, that xml list could be templated so they can knock out files that are not changed during an upgrade, and only affect files with changes.

Gaz