Forum Replies Created

Viewing 15 replies - 1 through 15 (of 51 total)
  • Thread Starter memitch08

    (@memitch08)

    I believe the problem is with 3.1 onward –

    I had no problem with permalinks before upgrading – it was only after the upgrade – so it seems funny that the server settings would change at the same time.

    I found I can eliminate the /blog slug from wp-admin/network/site-settings.php.

    But the category still will only work with the /?category_name=/example-cat permalink.

    Thanks!

    Thread Starter memitch08

    (@memitch08)

    So I didn’t realize that they had moved the network plugins – so I did have the remove /blog slug plugin activated through the network admin.

    I deactivated this – but I still get the same results – except now – I get the /blog slug in my permalinks. The categories now look like /blog/category/example-category and the result is a 404 page.

    When I set the permalinks to default – to reset – it goes to:
    /?cat=4779 – and I do not get a 404 page – the category is displayed.

    But when I change to custom permalinks – the permalinks for categories points to: /blog/category/ which results in a 404 page.

    Thanks!

    Thread Starter memitch08

    (@memitch08)

    Another note – it seems this issue has effected all of my sites. Not just this one.

    Thread Starter memitch08

    (@memitch08)

    I’m not using any plugins to mangle permalinks. I tried to use them but they didn’t work.

    I was using the remove /blog slug plugin before upgrade to 3.1. I don’t like having /blog in there. But that plugin is not active now. In fact – I am not entirely sure where the /blog slug went. It shows on the permalinks page – as a constant that cannot be edited – but none of the links show it.

    I should also note that adding the /blog slug in manually to the /category permalinks still return a 404.

    I have multisite – with mapped domains – and I have full control of all sites – so removing the /blog slug is not a threat as I see it.

    The problem is that /category/example-category/ returns a 404. I tried using the plugin that removed the /category slug – but that didn’t help either. I saw that the /?category_name=/example-category/ would go to the correct page – at some point during my trials and errors – so when I put ?category_name= into the category slug on the permalinks page – it works – but it’s ugly and I don’t like it. Also – I tried to put just “cat” into the category slug – but it too returned a 404.

    I don’t know if it’s linux or IIS – my host is BlueHost.

    Thanks!

    Lance & thecorkboard –

    Thanks for the information. I may look into the plugin suggestion more, but for the time being – I’ve corrected the registration issue I was having with the multi-network plugin thanks to this info here.

    removed :

    define( 'DOMAIN_CURRENT_SITE', 'memoirsite.com' );
    define( 'PATH_CURRENT_SITE', '/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );

    from the wp-config.php file.

    Note – my wp-config file did not have SITE_ID_CURRENT_SITE for some reason – so that was not removed.

    Now everything is working!

    Yes – I’m stuck there too.

    I have the multi-network plugin – and registrations all go to the mother site.

    I’ve tried the domain-mapping plugin in conjunction with this – and I can’t get it to work either.

    The domain-mapping plugin alone allows blog registrations on the sub-sites, but then they are not visible because I haven’t been able to figure out how to map them correctly.

    When I don’t use the domain-mapping plugin though – and let the multi-network plugin assign the domains, then registration doesn’t work properly?

    I’d really like to get this resolved where the multi-network plugin corrects the regisrtation issue – and the domain-mapping plugin isn’t needed.

    Thanks for the follow-up! :))

    Lance –

    Did you ever figure out the registration issue?

    Thanks!

    T

    :)) Thanks! It was actually your last post that helped me find the problem!

    Ok – Andrea – Don’t Shoot Me!

    But I fixed the problem –

    I thought I read that the file was to be called .htaccess.dist – so that is what I had it named.

    But in fact – it is supposed to be .htaccess

    In my FTP program – the .htaccess file is hidden – so when I uploaded the new .htaccess.dist – it just sat there and did nothing.

    So – I had to delete the hidden .htaccess – and upload the new one – and presto! Amazing I can’t believe my eyes – all of my images are back!

    Thanks for your patience and help! :))

    yes – those all work. I thought you were talking about the magically re-written ones.

    I don’t know if I said I have the *exact* same problem. 🙂 When I say I have the same problem I mean the outcome – not the cause. I don’t know code, and have been desperately trying to find an answer.

    So here is my problem as I know it in the simplest form:

    I noticed a problem after upgrading to 3.0 when all of my images disappeared. I’ve discovered that any directory named “files” returns a 404 page. Whether that directory is in the root folder – or in blogs.dir/#/files. The word “files” is being discriminated against – and that directory is inaccessible.

    Ok – thanks –

    1. Yes all on the same server
    2. Yes – removed the blogs.php
    3. Yes – updated the .htaccess file as directed
    4. I don’t know of any other pretty permalinks. I do know that when I changed the “files” directory to “uploads” directory – and changed all of the urls and updated the .htaccess file – then I could visit uploads/2010/06/file – but only on the root site – not on any others.

    🙁 That makes me sad.

    By the way- I just upgraded another site to 3.0 – and did not run any betas or RC’s – and that site has the same issue.

    I’ve had the exact same issue on 5 of my WPMU installs/upgrades.

    I don’t know what I could be doing any differently than anyone else – on all 5 of my installs/upgrades?

    I generally don’t personally use the media library anyway, but now need it for other users.

    http://wordpress.org/support/topic/413848?replies=3

    Aha!

    Look at this in ms-functions.php

    if (! is_subdomain_install() )
    		$illegal_names = array_merge($illegal_names, apply_filters( 'subdirectory_reserved_names', array( 'page', 'comments', 'blog', 'files', 'feed' ) ) );

    I have a subdiretory install which would explain why the term “files” is being discriminated against. Now the question is “how do I get a filter to fix it?” Anyone – someone?

    Aha!

    Look at this in ms-functions.php

    if (! is_subdomain_install() )
    		$illegal_names = array_merge($illegal_names, apply_filters( 'subdirectory_reserved_names', array( 'page', 'comments', 'blog', 'files', 'feed' ) ) );

    I have a subdiretory install. How do I get a filter to fix it? Anyone – someone?

    I’m having the same issue.

    I believe I’ve pinpointed the problem to the directory blogs.dir/#/files – the “files” directory for me is inaccessible.

    I worked around it by changing “files” to “uploads” in .htaccess, and in the site editor for upload path and Fileupload URL. This worked for my site 1 – but does not work for the rest of my sites – even if I follow the exact same procedure. A blogs.dir/#/files directory is created that is inaccessible?

Viewing 15 replies - 1 through 15 (of 51 total)