Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter kcyarn

    (@kcyarn)

    @ogalinski Sorry for not replying earlier. As a clarification, the post is as follows:

    * 1700 words
    * 15 links
    * 2 unordered lists
    * 1 ordered list
    * 1 image plus a feature image
    * 11 headers
    * 2 block quotes

    The writing process uses either markdown or Word as the client prefers. The sole concern is how long it takes to post prewritten content along with its prewritten metadata.

    Over the last three months, I’ve posted over 50 articles (500-2100 words) to client sites. Most use Gutenberg because it’s what their site upgraded to. (Although it feels like several change their editor every week…) Before posting the first review, I installed the bleeding edge plugin on a localhost and tested it. For prewritten long form content, the experience was the same as the earlier Gutenberg versions. No improvement.

    Long-term, I can see Gutenberg working as part of a site builder. It may even offer a better writing experience. I wouldn’t know. For long, prewritten pieces, it’s clunky.

    The uploads folder and its contents, including subfolders and images, needs 755 permissions, not 777.

    755 means the owner (usually www-data or whatever you named your webserver’s owner) has read/write/execute permissions. Everyone else has read/execute permissions. The search engines do not need to be able to write to your webserver to index it.

    I’ve also seen the 777 recommendations. It appears there is a misconception about the difference between the owner and the permissions. If the file/folder’s owner is the same user as the webserver, you can edit, write, and delete to the files from within WordPress without giving the world write access to your website.

    For example, on a linux server, you can login via ssh and type
    cd \var\www\sitename\wp-content
    ls -l

    A list of all files and folders within wp-content appears along with their owners. Under this list, look at the folder owners and verify they are all the same as your webserver. For example, www-data. If not, chown the entire directory to change the owner.

    chown -R www-data:www-data uploads

    The permissions remain set to 755, not 777, and uploads/theme editing now works.

    On my sites, owner mixups normally happen when I untar/unzip a file into my home directory and move it to my uploads directory.

    In your case, your problem might be in .htaccess. Check it for rewrite rules for .gif, .png, and .jpg.

    Google webmaster tools is a freebie, and it’s good for checking what Google’s crawlers can access. Webmaster’s error messages (or lack thereof) may give you more insight into what’s going on. I understand it helps if your xmlsitemap includes images, but I don’t know for certain because I’ve always included images in mine.

    Google also has images best practices that you may want to review.

Viewing 2 replies - 1 through 2 (of 2 total)