title no more centered

[scrambler]

OK, so this confirms what I suspected.

I can see the comment /* TEST fonts and custom CSS file */ inside the jumbled CSS that is at the end of the @media rule following the /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ section.

If I move your custom CSS following /* TEST fonts and custom CSS file */ before the /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ section it gets executed .

This means that the section /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ inside “weaverx-style-sheet-inline-css ” generated by weaver is corrupted!

The custom CSS that you enter in the global custom CSS rule box being added after that, it never gets executed.

So the question is why is the /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ section of the file corrupted (@weaver your help would be appreciated)

If you say your site was hacked, you need to consider that the corruption could come from the hack, and therefore that it may have been hacked way before 2 days ago.

If you can’t restore a much older version because of recent changes, you could try a cleanup with the procedure below

• Save all your weaver settings AND download a copy on your computer for good measure.
• Switch to a default WordPress theme
• Delete Weaver Xtreme and ALL weaver plugins.
• Redo the last WordPress update.
• Redownload a clean new Xtreme theme from Wordpess.org and activate
• redownload the Weaver plugins and activate
• Make sure the /* TEST fonts and custom CSS file */ is still at the top of the Custom CSS rule box

Post back

 

[beethoven]

Bonjour

• Save all your weaver settings AND download a copy on your computer for good measure.

done

• Switch to a default WordPress theme

done

• Delete Weaver Xtreme and ALL weaver plugins.

done including xtreme plus

• Redo the last WordPress update.

done

• Redownload a clean new Xtreme theme from Wordpess.org and activate

done

• redownload the Weaver plugins and activate

done including xtreme plus

• Make sure the /* TEST fonts and custom CSS file */ is still at the top of the Custom CSS rule box

It is

But the post titles are still  left aligned and not centered

[beethoven]

@scrambler, earlier you mentionned  Additional CSS WP settings. In two other sides I manage, vitaliteyoga.fr and teplitz-theatre.net that appears in Custom CSS but not in fncta-midipy.fr … why ?

[scrambler]

This reply has been accepted as the best answer.

Good news cleanup/reset worked and the CSS file is no longer corrupted, and so I can now clearly see what breaks it

Just before the TEST section title there is an invalid rule

input,textarea (line-heigh:0.5) /* TEST fonts and custom CSS file */

Which uses parenthesis () instead of curly brackets{} (edit: and a typo on height)

This is what breaks the CSS file, so nothing after that is taken into account.

So now it is about finding where this bad rule comes from.

I suspect a CSS+ box and I am going to try and find which one generates that rule.

You can search on your end. If we can’t find it, we will have to use the WordPress CSS box for your custom CSS

 

[scrambler]

The bad rule likely is in Main options > Content area > Text > Input Area BG CSS+ box

or the search boxes input CSS+ below that

[scrambler]

Regarding the WordPress CSS box, make sure the customizer is set to “Option level: full” and “Interface: where” modes

[User]

@Beethoven

In the above input,textarea (line-heigh:0.5) /* TEST fonts and custom CSS file */ the typo (line-heigh:0.5) instead of (line-height:0.5) suggests that this is a user-entered custom CSS.

Also that line has a <code class=”svelte-1fz0gqk fade-in”> <code class=”svelte-1fz0gqk fade-out”> which may help in finding the source.  To identify the exact plugin, you would need to inspect the  for the <code class=”svelte-1fz0gqk fade-in”> in the functions.php file.

Based on the search context, this specific naming convention ”svelte-1fz0gqk” (hash-based filenames) is characteristic of build tools like Vite or Rollup used in the following types of plugins:

Svelte WordPress Plugin Boilerplate: Projects such as dylanblokhuis/svelte-wordpress-plugin or Ebeldev/svelte-wordpress-plugin on GitHub serve as templates where Svelte components are compiled into a single hashed bundle and enqueued via PHP.

Custom Headless or Embedded Plugins: Developers using WPGraphQL to connect a SvelteKit or Svelte frontend to a WordPress backend often generate these hashed assets during the build process to embed Svelte apps into WordPress admin pages or frontend themes.

Your plugin: “Unique Headers: 2.1.3” seems to come close to those in description.

Then again, as this is a legacy site, it may be something left over from the past.

This plugin will help you identify left over bits: “Plugins Garbage Collector (Database Cleanup) ” https://wordpress.org/plugins/plugins-garbage-collector/

[beethoven]

@scrambler, the rule was indeed where you say. I changed the parenthesis  with curly brackets and Hourra ! The post titles are now centered ! So simple ! I don’t know where the error comes from, I didn’t make any changes to this css for years… but not matter, the issue is gone. Merci, merci, merci.
Thank you too @user I’ll have a look at the plugins-garbage-collector plugin, that may help another time.

[scrambler]

There was not only the curly bracket, but as @User mentioned a typo on heigh instead of height, in case you want that rule to work

[beethoven]

Uh-oh ! I did not see that. But the rule in this place is useless  as y see now. Nothing changes with or without this rule. So I deleted it

What I still not understand is why “Additional CSS WP settings”  not appear on Costumizer CSS for this side. Any idea ?

[User]

The Theme Customization Settings (options) are not the same as Custom CSS and as I understand are therefore stored differently.

Exactly what are you looking for that you have manually input into the customizer, but is not showing up there?

[scrambler]

@user, he says that on this site if he goes to Customize and Custom CSS section, the section “Additional CSS WP settings” is not present.

I have no idea what could cause that. An AI search says it can happen if you use a block theme which disables it.

Xtreme is not a block theme but may be some thing is still corrupted on your install.

It says to Check these possibilities:

• You are logged in as an Administrator. Editing CSS requires the appropriate permissions; an Editor or other restricted role may not see the option.seedprod

• The site is a WordPress multisite installation. Only the network Super Administrator may have CSS-editing permission.

• A security or hardening plugin has removed the unfiltered_html or related CSS capability.

• A setting in wp-config.php, particularly DISALLOW_UNFILTERED_HTML, is preventing CSS editing.seedprod

• A plugin is hiding or modifying the Customizer or Site Editor. Temporarily disable nonessential plugins to test.

[User]

@Scrambler

Thanks for that.  Yes, I guess I was too zoomed into the issue to grasp the wider picture….  😊

That said, it seems from what I’ve read that the file /wp-admin/customize.php  contains all the current contents of the “missing” menu option – “Additional CSS WP settings” UNLESS the theme has been changed.

It appears that a change of theme empties the CSS data from that file.  *** Which is probably why Xtreme warns not to use it:

Additional CSS – WP Setting : Help
“NOT RECOMMENDED! The standard WordPress “Additional CSS” rules defined here will NOT be saved with your Weaver Xtreme settings. If needed for some specialized circumstances, the “Additional CSS” rules are preserved across all Weaver Xtreme subthemes and settings versions on an individual site, but we suggest always using the “Global Custom CSS” option above.”

*** Just checked my main site customize.php and this all seems to be nonsense — other than the Xtreme warning….

So I have just moved all my data from “Additional CSS – WP Settings” to “Global Custom CSS”  and all works 100%.  The only difference is that the lines in “Global Custom CSS”  are not numbered.

[Author]

Posts