WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Help, permalink .htaccess is breaking CSS and Plugin (11 posts)

  1. music60
    Member
    Posted 3 years ago #

    Since changing permalink settings to "Month and name" the following problem occurs:

    1) Admin bar displaced from orginal position and now listed on the right hand side without any stylesheet taking effect

    2) Plugin WP Audio is no longer working, seems the Javascript files are also not linking properly.

    Any suggestions?

    Thanks for your help

  2. esmi
    Forum Moderator
    Posted 3 years ago #

    Have you tried:

    - deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

    - switching to the Twenty Ten theme to rule out any theme-specific problems.

    - resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

  3. music60
    Member
    Posted 3 years ago #

    Thanks esmi, I have tried your suggestions but same problem still persists. admin-bar is not loading correctly.

    From Safari script debugger on my site http://www.justsixtiesmusic.com the following error occurs on load:

    Failed to load resource: the server responded with a status of 403 (Forbidden)

    Files:
    admin-bar.css (location /wp-includes/css/admin-bar.css?ver=20110122)
    admin-bar.js (location /wp-includes/js/admin-bar.js?ver=20110131)
    l10n.js (location/wp-includes/js/l10n.js?ver=20101110)
    jquery.js (location /wp-includes/js/jquery/jquery.js?ver=1.4.4)
    jquery.fade.js (location /wp-content/themes/seven-five/scripts/jquery.fade.js)

  4. esmi
    Forum Moderator
    Posted 3 years ago #

    Try resetting your custom permalinks back to the default setting. If this works, then set a custom permalink structure back up again.

  5. music60
    Member
    Posted 3 years ago #

    After changing permalinks back to the default settings, the site is still throwing 403 error for same files.

    My .htaccess file included below, is there a rule to allow CSS and Javascript files explicitly, that might resolve this problem?

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # BEGIN WordPress

    # END WordPress

  6. esmi
    Forum Moderator
    Posted 3 years ago #

    No - there's no such rule. And there's nothing obviously wrong with your .htaccess file. Have you changed the permissions on any WordPress folders recently? Have your hosts?

  7. music60
    Member
    Posted 3 years ago #

    Thanks esmi. Current permissions settings are:

    Folder /wp-includes 755
    File /wp-includes/js/admin-bar.js 644

    Should they be different?

  8. esmi
    Forum Moderator
    Posted 3 years ago #

    No but you might want to check the folder within wp-includes.

  9. music60
    Member
    Posted 3 years ago #

    Have checked all folders under /wp-includes and they have the same permissions settings (folder 755, file 644).

    Using "View source" on the home page, I can see all scripts and css links are generated correctly. Tested adding a simple alert inside jQuery's document ready, only 'B' is fired. 'A' doesn't get fired because the jQuery.js is blocked.

    <script type="text/javascript">
    		$(document).ready(function(){
    			$.smoothAnchors(1000, "swing", false);
    				alert('a');
    		});
    
    		alert('B');
    	</script>

    How do I get around this 403 Forbidden issue? Please help ....

  10. music60
    Member
    Posted 3 years ago #

    This problem seems to be isolated to scripts located inside the /wp-includes directory.

    Everything under /wp-content are loaded fine. Thus /themes, /plugins are good.

    =/ Weird

  11. music60
    Member
    Posted 3 years ago #

    RESOLVED

    Restored /wp-includes directory with all it's contents from the server back up and it fixed this problem.

Topic Closed

This topic has been closed to new replies.

About this Topic