Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 23 replies - 26 through 48 (of 48 total)
  • @wildchild

    Participant

    @DBascent94: did you first had problems with 404 errors with all slugs?

    If you fixed that, how? I fixed it with re-installing but seem not to be able to restore the active database back into the new framework ….

    @wildchild

    Participant

    @John: I wish I could find out, there are more people with the same problem; although it seems to be (only) with sites already having data in them…

    @Andy: I’ve been copying over the database tables using phpmyadmin and by deleting entries I’ve found out the buddypress installation worked shortly. Too badly, I couldn’t redo the same routine …

    @wildchild

    Participant

    @Andy: Basically which you say is that a seamless upgrade with existing data is not possible; unless using Import/Export functions ? Or am I wrong?

    If so, This might be an important thing to mention for upgrades, because this wouldn’t be exactly an upgrade then but a new install with import…

    @wildchild

    Participant

    @andy: I’ve installed a testbuild which works perfectly. As soon as I started migrating in all wp_1_* data (no more, no less); the slugs gave the dreadfull 404 bug.

    The problem must be with the data; since a fresh install works perfectly and after the data gets imported, I get the nasty 404 bug.

    For production data, this is a bit sketchy, since I’m unable to use it ;)

    @wildchild

    Participant

    @Theeasybutton: I’ve tried installing a testbuild, it worked. As soon as I started migrating the database data, the slugs did not work anymore.

    I’ve only been replacing all wp_1_* data, changed the domain to test; no more, no less.

    The problem must be with the data; since a fresh install works perfectly and after the data gets imported, I get the nasty 404 bug.

    @wildchild

    Participant

    @theeasybutton: I’ve tried almost everything, except a clean test install. I’m probably forced to do one, although I’m not fully convinced it would fix the problem once I’d return it’s original data back ….

    I tried following the howto step-by-step to get RC2 implemented without luck at all

    @wildchild

    Participant

    @Andy: I\’ll be installing a test build very soon.

    My steps will be:

    • Install test WPMU+Buddypress
    • test
    • if this works, migrate all data
    • test
    • if this works, perfect .. problem solved
    • if it doesn\’t, it\’s a problem in the codebase…

    Everyone having this problem seems to be having existing data; which might be the first thing to look out for …

    It\’s for sure not the themebug with not accepting dashes in filenames; I tested, because my theme is called artistblog-v2 (yep, with a dash).

    The problem was not solved, I\’ve noticed a NEW problem even, with the preview not showing up in the right frame (rather in the full frame, making it unable to click the \”use theme\” button), but that could be my theme too which needs to be modified.

    Maybe something to think about, themes which don\’t get loaded in the lightbox, what about those to activate them ?

    @wildchild

    Participant

    @Dbascent: I’m going to do the same, prepare a test install, see how it goes and migrate it’s data back to the database. If it works and doesn’t work anymore after the data migration, it would be a database problem. If it wouldn’t fail, it’s a code-build problem…

    Normally I would never upgrade a live production system, although, the upgrades looked simple, easy and fast …

    not! ;)

    @wildchild

    Participant

    This looks exactly like the bug mentioned in https://buddypress.org/forums/topic.php?id=2314 ; did any of you find any solution for this ?

    @wildchild

    Participant

    I wonder if this has to do with the bug we’re having at https://buddypress.org/forums/topic.php?id=2314

    Anyone found a solution for 404 for any slugs ?

    @wildchild

    Participant

    @Dbascent94 & @mesgains: Do you use this on a production server or purely on a test install?

    I\’m wondering if this has to do with slugs and wordpress redirection and thinking about downgrading next week if no solution is found, because the minimal would be working then…

    @wildchild

    Participant

    I renamed the .htaccess file to see if it would solve the problem, it was automatically created to the original state afterwards.

    The problem is still not solved…

    @wildchild

    Participant

    @signaltrap: Did you find any solution for this problem yet ? Since I’m still searching as I write ….

    I’ve tried with all kinds of upgrades now without any slight difference at all …

    @wildchild

    Participant

    @natscrim: Check out “download zip” instead of clicking on the link ; because the link is pointing to the RC1 version while the “download zip” link is pointing to the right link.

    @wildchild

    Participant

    @Dbascent94: I’ve got the same problem, no preview is given just “activate”.

    Although the themes -are- activated, because I see the standard buddypress theme is activated.

    If I could only get rid of all those 404 errors on the normal buddypress functions ..

    @wildchild

    Participant

    I was running WordPress MU 2.7 before and have been manually upgrading ..

    bp-themes contains the original buddypress RC2 theme.

    @wildchild

    Participant

    I’ve backed up the entire wordpress directory, copied the database, downloaded the zip and overwritten everything. WordPress MU seems to work perfectly. I wonder if BuddyPress would break if I’d return it to it’s RC1 state with the newer WordPress MU installed?

    OT: I also wonder why there is an \”Inactive\” above my name, bug?

    @wildchild

    Participant

    I’ve upgraded by downloading the ZIP

    @wildchild

    Participant

    I’ve tried disabling -all- plugins running my site naked, although, it didn’t work at all;

    My first work was the upgrade of my existing theme to the new standards ; although that gives the same error as the “buddypress home RC2” theme.

    I’m not really convinced this is themes related…

    I’m 100% sure it’s not mu-plugins related either, because I’ve tried disabling all those by moving them away, disabling sunrise in wp-config.php and it did nothing else more than rendering a lot useless and giving the same 404 errors on the main domain.

    the plugins directory I moved too, backed up the database before moving them, logging in, lots of things not working anymore including the slugs, which were still giving the same 404 errors …

    restored the database, plugin directories, mu-plugins and enabled sunrise again, because it didn’t matter at all; except that my blog articles are currently working towards the world …

    @wildchild

    Participant

    – logs do not show any errors except the normal 404’s

    x.x.x.x – – [24/Apr/2009:13:10:28 +0200] “GET /members/wildchild/ HTTP/1.0” 404 9959

    – WPMU 2.7.1 is installed

    – Buddypress RC2 is installed for sure (https://buddypress.org/download/ has an error with the url in the title announcing the new version while pointing to the old! Only download zip is RC2 currently)

    – RC2 default templates and custom templates do not change anything at all

    – I’ve followed the upgrade instructions currently a dozen times

    Do you have by any chance the sunrise (domain mapping) or any redirect plugins installed?

    I tried by disabling them but I know WordPress is a little bit persistent on it’s redirections; if you got the same installed, it might be a good idea to look towards the mapping since the SLUGS are not working at all.

    @wildchild

    Participant

    I am having exactly the same problem, tested with the standard themes on http://beta.artistblog.me ; doesn’t work .. 404 errors on all SLUGS, starting at the one above.

    When testing this on the main domain, http://artistblog.me ; with my own themes, I get exactly the same errors. When putting the standard themes on the main domain … no luck ..

    It’s driving me crazy since the entire social networking is off-line …

    I’ve upgraded the themes and all…

    @wildchild

    Participant

    The ArtistPlug.NET social blogging network has got it’s first big change which is visible at http://blog.gowildchild.com and http://artistblog.me ; it’s also allowing 5 artistic users to it’s network till the beta period.

    http://visualsound.be has a buddypress compatible plug-in which allows soundcloud to implemented (also written for the network).

    Be sure to checkout this network for the common artist around the block!

    @wildchild

    Participant

    ArtistBlog.ME, ready to promote and aid the (upcoming) artist on the block, running Buddypress as social network component at http://www.artistblog.me ; which will be complemented with the ArtistPlug.ME component, soon.

    Enjoy! There are only limited spots available on this blog; only for and by artists wanting to defend their Creativity with their Common Rights…

Viewing 23 replies - 26 through 48 (of 48 total)
Skip to toolbar