Forum Replies Created

Viewing 15 replies - 91 through 105 (of 119 total)
  • Thread Starter xanathon

    (@xanathon)

    sigh…

    Thread Starter xanathon

    (@xanathon)

    This is the WP support forum, isn’t it?

    Thread Starter xanathon

    (@xanathon)

    I manually re-uploaded the german version of WP 2.9.2 but to no avail…

    Anyone?

    Thread Starter xanathon

    (@xanathon)

    Okay, known problem, found a solution:

    http://wordpress.org/extend/plugins/add-from-server/

    Thread Starter xanathon

    (@xanathon)

    Yes, I did that, the path to the file folder is set correct.

    Is the second path the complete URL or is it the serverpath?

    Thread Starter xanathon

    (@xanathon)

    They are already uploded, as I stated above.

    @otto42:

    I’ve had bad update experiences since the advent of 2.5. You are lucky that you never needed any backup. So why do the developers give the backup advise very clearly and definite when a new version comes out? They do not do this for nothing. And it is of course the right way to backup when installing a new version, this is agreed upon and good policy. Nice that you have server-backups, i have them too, they are made nightly. So I can tell my writers to rewrite the articles that were written after the last backup, when an upgrade goes wrong? No thanks.
    Not everyone has access to all server features. Some are even mostly clueless and just use WordPress. Especially for those the WPAU autoupdate including autobackups was a great feature.

    Plus: When people complain around here about updates gone wrong, the first answer almost always is: reinstall your backup. You will not really tell us, that backups are superfluent?

    I will state it again: WPAU works (worked, sadly) out of the box, the native WP2.7-update does not, at least on some installations. That is a fact and nothing you write here will change that.

    But those statements are the usual answers you give “on my installation it worked” is the mantra you repeat over and over when problems arise. Nice for you. Congrats. If I tell my customers: “you have no problem, my installations work” they will hang me out to dry. And with good cause. That’s not the way support works.

    It’s easy?

    No it’s not. Does not work (until now, still fiddling). WPAU worked out of the box.

    I do not want to be too critizising again, but… WP 2.7 is quite well done from the admins point of view. The new backend is really well done and great and gives not only back all the usability of pre 2.5 but expands it greatly.

    So I will not complain yet. But fact is: The upgrade from 2.6.x to 2.7 worked without any problem with WPAU. I deactivated WPAU and tried to upgrade to the newer 2.7 version and it does not seem to work without me having to change lots of permission-changes. WPAU did not need that.

    So there is probably some work to do with the autoupdate.

    Edit: Plus: WPAU did an autobackup of the database and all the blog files. With the WP updater I have to do this manually… So I still hope, there will be an 2.7-update for WPAU…

    I agree. Update via WPAU worked without any problems. After that – however – I still had to upgrade to a newer version of WP2.7 and tried the build-in upgrader – which failed. It seems there are some permission problems, still trying to figure this out.

    Has someone an information if WPAU will still work in the future? Since the native WP update seems bitchy…

    xanathon

    (@xanathon)

    Data redundancy is never a good thing, even if modern databases are able to handle big amounts of data. Plus: not everyone has access to databases that have unlimited space, especially on shared hosting.

    The sensible course of action would have been to disable versioning by default and let the users who really need it activate it.

    That way no one would have to deal with clogged databases.

    Thread Starter xanathon

    (@xanathon)

    Then: good bye WordPress. It was fun while it lasted.

    Aside from the fact that there are hacks for the admin backend to get the functionality of posting back, there are no alternatives to the awful bad and unergonomic image uploader and the fact that my library of images can no longer be used since the developers choose to change image handling, filenames and folder. Why they did so eludes me completly.

    No way I use 2.5.x

    Thread Starter xanathon

    (@xanathon)

    Schlaumeier :oP

    Thread Starter xanathon

    (@xanathon)

    After quite some fiddling I managed to reinstall the database- and filebackups of my 2.3.3 installation.

    What shall I say: Everything works fine again, plus I’ve got back a usable and ergonomic backend.

    Now I have time to look for an alternative to WordPress in the case that the devs stick with their wrong design- and code- decisions and there really will be no longer security-updates created for 2.3.3, as announced.

    Frankly, I do not care if 2.5 was virtually rewritten from scratch and is praised as much better than before. Too many things do simply not work with the same server- and client-config as before. The problems lie in the new version and you cannot in earnest demand from all users to bug their hosters until they change their server-config to the developers liking. That is plain stupid, i you forgive me to express my opinion in clearness.

    I have the same problem

    But as I do not have access to the server settings or shell access (the blog is not hosted by me) I’m only able to set CHMOD and not CHOWN.

    Why the developer choose to change the behaviour like that absolutely eludes me, it makes no sense at all. 2.3.3 worked fine, 2.5 is a desaster.

    The same goes to the decision that we cannot reuse the images already online (before the installation of 2.5). superfluous redundancy and not very efficient. Not everyone has unlimited server space.

    Thread Starter xanathon

    (@xanathon)

    Hello Rongo, thanks for your reply. Yes, I’ve read your comments about the image quality while I’ve searched for a solution for my problems.

    Regarding the scaling: nope, the problem also exists with newly uploaded images.

    Aside from that it’s absolutely crackbrained by the developers to code an update that is not able to use the existing image repository. Now I have to reupload pictures that are already on the server just to get them as a thumbnail again? Gimme a break!

    I certainly hope someone will take over the sourcecode of 2.3.3 and create a fork of WordPress that works again and again has the old ergonomy and usability in the backend and editor.

Viewing 15 replies - 91 through 105 (of 119 total)