Forum Replies Created

Viewing 15 replies - 1 through 15 (of 1,544 total)
  • @merridennis You’re welcome. I’m glad it worked for you.

    There are lots of apps for doing file comparisons, you shouldn’t ever have to do it manually?

    LOL I’ll bet you did cringe. I don’t blame you a bit. Manually comparing all those files would be a nightmare.

    I didn’t mean a manual comparison of the files, I meant to use the Linux app “diff” which would do the comparison for you in short order, listing all the files that differ. You’d need to exclude some folders which would naturally differ, like /wp-content/uploads and your theme and plugin folders, etc. The diff package is usually installed on most servers, so it’s probably already there waiting for you.

    If it doesn’t turn anything up with the core files, you could try using it to compare fresh versions of your theme(s) and/or plugins.

    I’m with you, there has to be something in there that’s interfering. I guess you could also install a plugin that will do a file check for you.

    I’m stumped too. Hopefully, one of the gurus here will chime in.

    You said in the original post that, “all the files in the install are those provided in 5.4.2.” Have you run diff on the install files and a set of 5.4.2 files uploaded to a different directory on the server, or are you just basing that on having done the manual install procedure?

    linux4me2

    (@linux4me2)

    Why not just change the extension from .csv to .txt?

    A .csv file is just a text file, so it should work. Most browsers will open a .txt file rather than prompting for a download.

    By converting to pipe-delimited, do you mean changing all the commas to pipes, or changing the line feeds to pipes?

    Either way, you can use a text editor to do a find-and-replace to accomplish that if you’re just doing a few files. Your spreadsheet or database program may also allow you to substitute the column or line feed separator to a pipe before exporting the file, as well.

    You might also want to google for “convert csv to html” to see all the options for converting the file to an HTML table.

    linux4me2

    (@linux4me2)

    Just browse to the video you want to embed on Dailymotion. Take a look at the URL in your browser’s address bar. The end of the URL will look something like the following:

    
    .../video/x7vpb6r?playlist=x6lgtp
    

    copy the URL up to the “?”:

    
    .../video/x7vpb6r
    

    Add a Video block to your post or page, then click on “Insert from URL.” Paste the URL from Dailymotion, then click Enter.

    You should be good to go.

    Try dismissing the notice from the WooCommerce -> Orders page. I couldn’t dismiss it on several sites either, but was able to do so without a jQuery Migrate plugin by going to the Orders page first and then clicking the button to “Remove legacy coupon menu.”

    It may be coincidence, but I’ve finally gotten both the “WooCommerce database update done” and Coupon location notices to go away by dismissing them from the Orders page. It has worked on three sites.

    The error message appears to be unrelated. I’ve had the database update complete on two sites, the error still appeared, but I was able to dismiss the “WooCommerce database update done” notice on those two sites.

    All the sites are on the same server.

    That is seriously strange. The only other thing I can think of is that some caching is going on that is caching your Admin pages, but the WordPress-specific caching plugins I’ve used don’t cache the admin side. Maybe if you’re using some server-side caching or a CDN it’s showing you an old, cached version?

    The really weird part is that it showed 5.4.2 after you did the manual upgrade and then reverted to showing the wrong version.

    @plarry I am pretty certain I cleared my browser cache when I was trying to figure this out. I’m using Firefox, and Ctrl+F5 seems to reliably clear the browser cache.

    I just tested a bit more by commenting out my code that hides the two pages.

    I reloaded the page after uploading the new functions.php when I wasn’t logged in, so caching with WP Super Cache was active. I still saw the old page with the two pages hidden from the sitemap.

    I cleared the browser cache (Ctrl+F5), and still didn’t see the pages.

    I logged in so caching was disabled, and refreshed the page. The two pages were back in the sitemap.

    I then restored the code, refreshed my browser–but didn’t clear the browser cache–while still logged in and the pages were gone from the sitemap.

    I don’t know what the cause was. It does seem like a caching issue, but I can’t reproduce it now. I haven’t looked at the code, but maybe the sitemap is only regenerated periodically via wp-cron? That’s the only other explanation I can think of.

    On the positive side, it’s working now, and I’ve used the core sitemaps on several other sites without the issue recurring.

    Okay, I’m thinking it may be that the database update wasn’t done at some point between April and now.

    Try running the following query in phpMyAdmin, changing “wp_options” to match your database:

    
    SELECT * FROM wp_options where option_name = 'db_version'
    

    It should return an option_value that looks nothing like the WP version; however, you can compare the option_value to this table and find the version it translates to.

    • This reply was modified 1 month, 2 weeks ago by linux4me2. Reason: removed code tags from query

    That is an interesting issue.

    I think older versions of WP had the version in the readme.html file, but I don’t think the Admin side got it from there.

    I would try using the file manager from your hosting control panel (or download the file with Filezilla) and look at the file /wp-includes/version.php. There is a line in there like this:

    
    $wp_version = '5.5';
    

    What does yours say?

    @dynamiczach Thanks for the quick reply. I will give the upgrade a whirl.

Viewing 15 replies - 1 through 15 (of 1,544 total)