festusdog

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • Thread Starter festusdog

    (@festusdog)

    what impact is there, if I disable the Meow Lightbox cache?

    Thread Starter festusdog

    (@festusdog)

    It would also be nice to know where the settings for the Lightbox are stored at. I deleted the plugin, made sure that the directory was gone, then reinstalled the plugin… and all the settings were exactly as I had left them. (For example, I had disabled the “LENS” simply the exif data displayed). I would have expected the settings to revert to default after a delete and reinstall?

    Deleting & reinstalling the plugin also did not help with the problem of not being able to RESET.

    I would have thought that the setting were stored in the Lightbox plugin folder. I also glanced in the WP database and did not see anything that stood out as relevant to the Meow Lightbox plugin.

    • This reply was modified 1 year ago by festusdog.
    Thread Starter festusdog

    (@festusdog)

    This is definitely a CACHE problem, because when I DISABLE the cache, the EXIF works properly. When I enable cache, the EXIF is “weird” (as described above) and also clicking RESET does nothing.

    So please advise how to fix the cache problem and fix the resetting cache problem. Thanks.

    Also, for example, when the exif is weird, the word “ISO” never appears in front of the ISO number.

    • This reply was modified 1 year ago by festusdog.

    Same here. I was testing my website tonight, also hosted by Hostinger (shared hosting account), and after maybe 9 or 10 scans I am getting the …unable to scan, timeout reached… error message.

    FWIW, I was using the Sucuri website to make the test, not the plugin.

    Thread Starter festusdog

    (@festusdog)

    And FYI, that is found in your header.php file

    Thread Starter festusdog

    (@festusdog)

    OK, I will answer the question myself, and share with anyone else who may be having same problem.

    In your HEAD section, you are missing a PHP statement.

    Example of what it should have:

    <head>
    <!– First add the elements you need in <head>; then last, add: –>
    <?php wp_head(); ?>
    </head>

    So, the problem is that I was missing the line:
    <?php wp_head(); ?>

    Putting that directly before the </head> tage fixes the problem.

    Thread Starter festusdog

    (@festusdog)

    Also, further information… the error message does not display if I am logged into the site and viewing the site. But logged out — the way any visitor would view the site — the error message is printed.

    I want to solve the problem, not just hide the error message.

    Thread Starter festusdog

    (@festusdog)

    ok, understood. I contacted 1&1 and their support says that they have no service issues relating to WP updates, and also that they do not cache any of my sites or cache anything relating to my sites.

    So I am at a standstill….

    Thread Starter festusdog

    (@festusdog)

    debug log, with sensitive info redacted:

    
### WordPress ###

Version: 5.1
Language: en_US
Permalink structure: /%postname%/
Is this site using HTTPS?: No
Can anyone register on this site?: No
Default comment status: closed
Is this a multisite?: No
User Count: 1
Communication with www.remarpro.com: www.remarpro.com is reachable
Create loopback requests: The loopback request to your site completed successfully.

### Installation size ###

Uploads Directory: 1.51 MB
Themes Directory: 1.38 MB
Plugins Directory: 13.41 MB
Database size: 2.34 MB
Whole WordPress Directory: 57.40 MB
Total installation size: 59.74 MB

### Active Theme ###

Name: 
Version: 
Author: Anonymous
Author website: Undefined
Parent theme: Not a child theme
Supported theme features: widgets

### Other themes (1) ###

Twenty Nineteen (twentynineteen): Version 1.3 by the WordPress team

### Active Plugins (2) ###

Health Check & Troubleshooting: Version 1.2.5 by The www.remarpro.com community
Wordfence Security: Version 7.2.2 by Wordfence

### Inactive Plugins (2) ###

WP-DBManager: Version 2.79.2 by Lester 'GaMerZ' Chan
WP-Optimize: Version 2.2.12 by David Anderson, Ruhani Rabin, Team Updraft

### Media handling ###

Active editor: WP_Image_Editor_GD
Imagick Module Version: Imagick not available
ImageMagick Version: Imagick not available
GD Version: bundled (2.1.0 compatible)
Ghostscript Version: 9.26

### Server ###

Server architecture: Linux 3.16.0-ui18276.29-uiabi1-infong-amd64 x86_64
Web Server Software: Apache
PHP Version: 7.3.2 (Supports 64bit values)
PHP SAPI: cgi-fcgi
PHP max input variables: 5000
PHP time limit: 50000
PHP memory limit: -1
Max input time: -1
Upload max filesize: 64M
PHP post max size: 64M
cURL Version: 7.38.0 OpenSSL/1.0.1t
SUHOSIN installed: No
Is the Imagick library available: No
htaccess rules: Custom rules have been added to your htaccess file

### Database ###

Extension: mysqli
Server version: 5.5.60-0+deb7u1-log
Client version: mysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $
Database prefix: xxxxxx_

### WordPress Constants ###

ABSPATH: /homepages/13/d123456789/htdocs/xxxxxx/
WP_HOME: Undefined
WP_SITEURL: Undefined
WP_DEBUG: Disabled
WP_MAX_MEMORY_LIMIT: -1
WP_DEBUG_DISPLAY: Enabled
WP_DEBUG_LOG: Disabled
SCRIPT_DEBUG: Disabled
WP_CACHE: Disabled
CONCATENATE_SCRIPTS: Undefined
COMPRESS_SCRIPTS: Undefined
COMPRESS_CSS: Undefined
WP_LOCAL_DEV: Undefined

### Filesystem Permissions ###

The main WordPress directory: Writable
The wp-content directory: Writable
The uploads directory: Writable
The plugins directory: Writable
The themes directory: Writable
    Thread Starter festusdog

    (@festusdog)

    To be clear, the problem is not resolved. I still don’t know what is causing the database to not update properly.

    So I am looking for answers to that. Thanks in advance.

    Thread Starter festusdog

    (@festusdog)

    Hi everyone,
    thanks for working with me to eventually resolve this problem.

    Replying to a few points above:

    1) I installed Health Check, and nothing was flagged except “5.5.60-0+deb7u1-log
    – For performance and security reasons, we strongly recommend running MySQL version 5.6 or higher. ”

    Also, the filesystem permissions are all writable.

    Here is the server info:
    Server architecture Linux 3.16.0-ui18276.29-uiabi1-infong-amd64 x86_64
    Web Server Software Apache
    PHP Version 7.3.2 (Supports 64bit values)
    PHP SAPI cgi-fcgi
    PHP max input variables 5000
    PHP time limit 50000
    PHP memory limit -1
    Max input time -1
    Upload max filesize 64M
    PHP post max size 64M
    cURL Version 7.38.0 OpenSSL/1.0.1t
    SUHOSIN installed No
    Is the Imagick library available No
    htaccess rules Custom rules have been added to your htaccess file

    2) I would be happy to blame this on 1&1, and while that may prove to be true, it really seems unlikely. I have run these 2 WP installs since 2007 and even was using auto updates before they were mainstream, via wp config entry “define( ‘WP_AUTO_UPDATE_CORE’, true );”

    So, 11 years, no issues until 5.0 was released.

    Thus, that could be coincidence that 1&1 started having a new problem exactly when 5.0 was released, but it seems more likely that something else is going on.

    3) FYI – both sites are VERY LOW TRAFFIC

    4) any suggestions as to things to change, or things to check, please advise.

    Thread Starter festusdog

    (@festusdog)

    No, not a theme.

    The solution was same as last time, but this is a reoccurring problem since 5.0 was released, so I require a PERMANENT FIX.

    The solution was, again, to manually update the db_version in phpMyAdmin to the version number that I find in the version.php in wp-includes directory:

    $wp_db_version = 44719;

    But honestly, this is nonsense to have to manually fix this every time a upgrade is done anymore. Why is the database NOT properly changing the db_version entry?

    So what needs to be fixed? Like I said, i don’t run plugins on one of the sites, and that one has SAME PROBLEM.

    nicolafurini said it all, and so have I.

    Never an issue before 5.0, and that goes back many years and many updates.

    We will see whether more users have this problem over the next weeks and months.

    Also, browser cache was ~~OBVIOUSLY~~ not an issue here, thus I did not consider it as part of any serious relevant discussion. You seem to assume that (we) are not experienced with server config, apache, php, or WP installations in general, and that is simply not an assumption to make.

    @otto42,

    Besides, I assume that you mean “clear cache” under the assumption that I use some type of WP Cache plugin. I DO NOT.

    I have very few plugins, most are disabled when not in use. All I have are WP-DBManager and WP-Optimize and Disable Emojis. The first two are disabled when not in use. And one website has the Wordfence firewall. That’s it. No caches, no other plugins.

    So your assumptions are wrong.

    ok.

    Let’s think…. I have been using WP since 2007. Auto upgrade ever since it was available, and I had even set the flag to auto upgrade before it was a default feature.

    Never an issue.

    Never “cleared a cache”, nor ever HEARD that in order for AUTO UPGRADE to work that I was supposed to ~MANUALLY~ CLEAR A CACHE/s (!!, yeah, that’s logical….)

    So now two of my websites have (at least) a partially failed auto-upgrade install to 5.0 that prevents logging into the dashboard. Other users are reporting the same problem.

    But you think there is not a bug. Ok, whatever you say. I guess it is my (and other users) fault that the auto-upgrade failed, even though there is NOTHING NON-STANDARD AT ALL about either of my installations.

    I suspect that a lot of low-traffic websites will not discover this bug for quite a while. Had I not tried to log-in to see “what’s up” I would not know (yet) that the upgrade is at least partially failed. The external websites are loading fine, so no obvious sign that anything is amiss.

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