Forum Replies Created

Viewing 6 replies - 16 through 21 (of 21 total)
  • Try LiveFyre:

    http://www.livefyre.com/install/

    I use it extensively for my own site as well as client sites. Automatically blocks spam and allows comments via social profiles. Not to mention it’s interface is top notch.

    Ah, seems you correctly reset the permissions. The /wp-includes is correctly blocked and your images are showing 🙂

    Not sure about MAMP, since I use Uniform Server for localhost development, and prefer the find-and-replace method with the raw SQL when migrating, but here’s a post that specifically mentions MAMP:

    http://www.wpbeginner.com/wp-tutorials/how-to-move-wordpress-from-local-server-to-live-site/

    Should be of use (if not as just as a reference) if things go south.

    Forum: Installing WordPress
    In reply to: Login Error

    Looks like some sort of permission error.

    For example, the /wp-includes folder is NOT supposed to have a directory listing, yet if you goto adam…..com/wp-includes you see a directory listing.

    It may be a problem with the .htaccess file and/or the permissions of the folders before or during the installation.

    Did you install with a 1-click Install script?

    Either way, try logging into your Control Panel and setting the entire public_html or wordpress folder to 775 and see if it works.

    Also, have a look at the Codex:

    http://codex.wordpress.org/htaccess

    And ensure your .htaccess has those rules. I do feel it’s a problem with the folder permissions though. 775 everything and see what happens first.

    your /wp-content has correct permissions but the /uploads folder and the corresponding images called from within the webpage or directly give an error 500.

    Maybe check the permissions for the folder? Set them to 775 for the /uploads folder and all files and see if it works.

    Are thumbnails showing up in the Media Library?

    Yes, you should remove them, since the .htaccess file should contain minimal settings. Apache doesn’t play well with conflicting rules.

    .htaccess rules are quite complicated, as you can tell by the sheer number of rewrite conditions WP Super Cache’s inserts when enabling caching via mod_rewrite, and thus those rules are very canonical in nature.

    Simply put, an .htaccess file shouldn’t contain any rules that are absolutely not necessary, as they affect everything from page serving to how web crawlers and malware purposefully access and index your website. I recommend you delete them or at least comment them out by using the “#” character at the beginning of each line.

Viewing 6 replies - 16 through 21 (of 21 total)