- This topic has 42 replies, 10 voices, and was last updated 2 weeks, 6 days ago by
.
-
Posts
-
I am not seeing what you are describing.
You may just have a cache issue, Clear ALL your caches (browser, plugin, Cloudflare…) and see if it clears up
As scrambler said, I just don’t know how settings could be changed. In the normal course of operation, Any site keeps the same SQL database. Both Weaver Xtreme 5 and 6 use the same database entry. When logged in as a admin (which you must be to update the theme), settings are saved in the same place.
So the first time you switch from 5 to 6 (normally by the standard WP theme update process), not much should happen. While Weaver Xteme 5 created and used files in the site/wp-content/uploads/weaver5-subthemes file to save some .css files, Weaver Xtreme 6 no longer needs or uses .css file. Instead, all CSS rules are compacted and added directly to the HTML output. (The only exception is for supporting the Classic Editor which turns out must use a .css file to add CSS styling. But that affects only the Classic Editor.)
So I’m stumped. Some sort of caching issue?
My message was :
Thank you both @weaver and @scrambler. I saw “around line 833” but I’m not sure to understand “around” Where do I put the code ? before line 833 ? I’m not a php specialist and would not do something wrong.
And someone added :
If that is the case, you may want to try and delete/redo the bad menu, or wait for a WP fix…
That is not a very nice answer ! I hoped a bit more
I did not mean to be rude, sorry if it came out that way.
I am just saying that if you are not comfortable with PHP, you may not want to mess with WordPress system files, as you can botch your installation.
Ultimately your choice 🙂
@weaver would have to comment on the fix detailsRE: Showing date – What is showing is the date the post was last updated. You have checked the options to hide the post date, author, categories, tags, and permalink. There never has been an additional option to hide the updated date. Could be considered a bug. But there is an easy fix – simply check the option Hide top post meta info line in the Post Meta Info Lines Visibility section. I’m pretty sure that “feature” has been present all along, but you (or me, actually) never noticed that Updated Date item because it doesn’t show if a post doesn’t happen to get updated. I will not add that since the Hide top post meta info line option handles it.
RE: Missing fonts. The really is an issue with your CDN. I have found a work around, but it is not entirely acceptable. I will add an option to “Do Not Self-host Google Fonts” the will return to the old way of loading fonts from Google directly. That is not great for 2 reasons: it breaks EU GDPR regs and it is slower. That will probability fix your issue, however. It is possible that then adding the OMGF plugin would fix the issue with your CDN and the CORS policy.
EDIT: I just found the appropriate StackPath help page on this topic! It seems it can be fixed.
https://support.stackpath.com/hc/en-us/articles/360001075886-Using-StackpathCDN-with-Web-Fonts
But I would hope the real solution is to find a setting on your StackPath CDN provider account that allows the ‘*, *’ CORS protocol for specified cached content. There may even be a simple setting that handles font files differently.
So, I’d like to know if you can find such a setting, and if it cures your problem or not. If there is no easy solution, then I’ll release WEver 6.0.2 with the use Google to host option. It does look like this may be a general issue, but I’m just not sure if it should be considered a theme theme or not. But without being able to test it (Cloudflare does not seem to have any CORS issue.)
Your feedback would be most helpful.
@scrambler, my problem is resolved by deleting and remaking the whole menu. It took time but worked. Thank you
Thank you for the report back. Your results by remaking your menu does seem to confirm that the real issue was having a missing or corrupted item in the menu list. So this is indeed a WordPress core bug, and I hope they will fix the issue is an upcoming version of WordPress. I will actually pass on your experience to the WP team.
Messing with WP core files would require editing the file in question using the Editor from your hosting cPanel or other tool that allows direct editing of the file. If you haven’t edited PHP files before, it is probably best you spent the time to remake our menu because WP will no doubt have a 6.2.1 version fairly soon, and it probably won’t have the bug fixed, so you’d be back to a broken menu.
Hi,
Have the strong impression my search form ( [search] with X-Plus 6.2) is no longer working. Located on Info Bar @ https://www.mmwb.nl
Any idea?
- The topic ‘ Weaver Xtreme 6.2 Problem reports’ is closed to new replies.