Forum Replies Created

Viewing 15 replies - 1 through 15 (of 25 total)
  • Thread Starter Lappert

    (@lappert)

    I’m the original poster. Glad to have some company, and no, I don’t feel spammed (although Steve, thanks for the good intentions).

    I haven’t encountered any problems from having deleted the two left-behind files, but in many cases problems may take many months to be seen.

    Thread Starter Lappert

    (@lappert)

    Thank you. That seems to be working. I assume you mean to reinstall the complete 5.3.1 update as there is no button for just “core files.”

    I got the same email notice for a second WP install, so I’m assuming this is just a glitch in the update process, or a false positive.

    Several other WP installs haven’t yet generated the notice, but that could be due to Wordfence not having scanned them yet. So I’m deleting the two files in all installs just in case.

    Thanks again.

    Thread Starter Lappert

    (@lappert)

    Thanks for your reply.

    The only IP whitelisted is mine. No others.

    I am seeing lockouts, but strangely, the IPs I have blacklisted are getting through. There doesn’t seem to be a way for a permanent lockout. This is even stranger as some of those IPs that get through are listed as permanent banned through another plugin (IThemes Security).

    Thread Starter Lappert

    (@lappert)

    Thank you for the suggestion, but I already searched the plugin database for error (and also for access) logs. I was hoping for someone with expertise would have an idea here.

    The search (for just error) brings up over 2,000 results, with many for Activity, User, 404 and almost everything except what I’m looking for. Chances are many of the plugins are not compatible with WP5.1 or continue active development.

    Thread Starter Lappert

    (@lappert)

    Tanks for your reply, but not using cPanel or XAMPP. Just using plain old Apache2 (I guess it would be LAMP) Debian install.

    Years ago we used Accesswatch – I mean in the 90’s, no WP. For a while we also used AWstats, again pre-WP and before it was tied to cPanel.

    So just looking for a simple log parser showing overall traffic, ad hopefully broken down by page.

    Thanks

    Thread Starter Lappert

    (@lappert)

    I had hoped to see some replies, but none so far.

    Just in case … reading other posts … I deleted the newest version of CF7 and installed ver. 5.05 to avoid any complications with the captcha 3 controversy (I hadn’t set up any captcha, but just in case).

    I also checked ownership and permissions. All seem OK. Everything owner/group of www-data. Folder Perm: 755

    Alas, the problem still exists and all I get are the 404.

    Thread Starter Lappert

    (@lappert)

    As a followup, when I try to go to mydomain.com, the following appears in the access log for this domain.

    XXX.XXX.XXX.XXX – – [26/Feb/2019:20:44:47 -0500] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 665 “http://mydomain.com/wp-admin/post.php?post=46&action=edit” “Mozilla/5.$
    XXX.XXX.XXX.XXX – – [26/Feb/2019:20:44:51 -0500] “GET /contact/ HTTP/1.1” 404 503 “http://mydomain.com/wp-admin/post.php?post=46&action=edit” “Mozilla/5.0 (X11; Linux x8$
    XXX.XXX.XXX.XXX – – [26/Feb/2019:20:44:51 -0500] “GET /favicon.ico HTTP/1.1” 200 295 “http://mydomain.com/contact/” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36”

    XXX.XXX.XXX.XXX = myIP

    Nothing appears in the error.log for this domain.

    Thread Starter Lappert

    (@lappert)

    I wanted to get back to this thread. I was able to find a solution, although not in the approach we’ve discussed.

    It actually was rather simple. This applies to Debian (I’m running Jessie but it should probably work for wheezy) and for those who are using Apache 2 webserver. For other webservers, I can’t say this will work, but one should figure out how to apply it in your cases.

    Although we own and run our own server, we have access to upstream techs. They looked at it and suggested we change

      Allowoverride None

    to

      Allowoverride All

    in the virtual server configuration.

    In Apache 2, that would be in the .conf file for each virtual domain in the Sites-Available directory:

    /etc/Apache2/sites-available/mydomain.conf

    In that file I changed it twice:

    <Directory />
    Options FollowSymLinks
    AllowOverride All
    </Directory>

    <Directory /home/mydomain/>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride All
    Require all granted
    </Directory>

    Once the change is made, apache needs to be restarted.

    It seems this is necessary as Permalinks rewrites the .htaccess file each time a change is made. So the changes need to be able to override the original settings.

    If your permalinks is not going to change, it might be possible to put the contents of the .htaccess file into the mydomain.conf file and avoid the performance hit. However, I haven’t tried that.

    Thread Starter Lappert

    (@lappert)

    And as I cycle among the permalink options under Settings, the DB in phpMyAdmin also updates.

    But remember the problem is that whatever option is chosen (other than ‘plain’), it results in a 404 Not Found for the post or page.

    I can’t believe the WP developers never dealt with this – or fixed it. A Google search reveals hundred of reported similar problems.

    OK, it’s late and I need to grab some sleep. Will pick it up tomorrow. Thank you.

    Thread Starter Lappert

    (@lappert)

    ok, reinstalled phpmyadmin

    My database
    WP_options
    Option ID 28

    Edit | Copy | Delete | 28 | permalink_structure | /%postname%/ | yes

    I didn’t change anything.

    Thread Starter Lappert

    (@lappert)

    Well part of my immediate issue is that I can’t select Browse in phpMyAdmin. When I do I get a red box that says:

    Error in Processing Request
    Error code: 500
    Error text: Internal Server Error

    I’m looking into this. Will be back 🙁

    Thread Starter Lappert

    (@lappert)

    1. Yes, both WordPress Address (URL) and Site Address (URL):
    both set to http://tenantnet.net

    2. + index.php + wp-config.php + .htaccess all in root?

    Yes, here’s the directory from doc root:

    /home/tenant-new/public_html/wp-admin/
    /home/tenant-new/public_html/wp-content/
    /home/tenant-new/public_html/wp-includes/
    /home/tenant-new/public_html/.htaccess
    /home/tenant-new/public_html/favicon.ico
    /home/tenant-new/public_html/index.php
    /home/tenant-new/public_html/license.txt
    /home/tenant-new/public_html/phpinfo.php
    /home/tenant-new/public_html/readme.html
    /home/tenant-new/public_html/wp-activate.php
    /home/tenant-new/public_html/wp-blog-header.php
    /home/tenant-new/public_html/wp-comments-post.php
    /home/tenant-new/public_html/wp-config-sample.php
    /home/tenant-new/public_html/wp-config.php
    /home/tenant-new/public_html/wp-cron.php
    /home/tenant-new/public_html/wp-links-opml.php
    /home/tenant-new/public_html/wp-load.php
    /home/tenant-new/public_html/wp-login.php
    /home/tenant-new/public_html/wp-mail.php
    /home/tenant-new/public_html/wp-settings.php
    /home/tenant-new/public_html/wp-signup.php
    /home/tenant-new/public_html/wp-trackback.php
    /home/tenant-new/public_html/xmlrpc.php

    3. The contents of .htaccess are generated by WP:

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

    # END WordPress

    4. Permalinks – radio button is set at Post name, described as http://tenantnet.net/sample-post/

    However, when that is set, the Custom Structure radio button becomes /%postname%/

    5. I don’t use cPanel. But I do use phpMyAdmin
    But I can’t find “permalink structure”
    There is no table with that name.
    Also in phpMyAdmin I don’t see Options

    (I’m not that well-versed with phpMyAdmin. Are you looking for a specific table, field, ???)

    However, I found https://goo.gl/su0Hmq that describes permalink_structure in the table wp_options. However, I still can’t find permalink_structure.

    I’ll keep looking.

    Thread Starter Lappert

    (@lappert)

    This problem occurs with a new virgin install. No new posts, pages, themes or plugins have been added … just what is in the WP download.

    I’ve done a good bit of research on this and there are hundreds of reports of this problem on Google, as well as on Youtube. The purported fix, to set permalinks back to plain, gives you a URL that’s really not acceptable for many.

    To some, setting the URL with month, year and day is OK.

    Trying to get it to work with a preferred URL format of just post name leads to increased frustration — it doesn’t work.

    So with all this, has anyone reported this as a bug to WordPress core, and have there been efforts to address it? Some of the incidents reported go back at least ten years.

    This is frustrating as I gave up installing new sites in Drupal in favor of WP. But this is a fundamental problem.

    Thread Starter Lappert

    (@lappert)

    Yes, it is the same URL for both.

    We are our own host … we have our own server, running Debian Jessie with Apache.

    See details at http://tenantnet.net/phpinfo.php

    Thread Starter Lappert

    (@lappert)

    http://tenantnet.net/

    But this is the new virgin install from this morning. The only thing on it is the Hello World post.

    As you will see, the post at http://tenantnet.net/hello-world/
    leads to a 404.

    When installed, the permalinks are set to Month and Name, and posts may be viewed. But when changed to Post-name, they become unviewable. The only was to get out of that is to set the default/plain to “?p=123” and so on.

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