rima
Forum Replies Created
-
I updated. I will keep you posted. Thank you very much, your support is very appreciated!
I did not downgrade, always been on 7.4. I saw the fatal error over this past week and upgraded to the latest version yesterday. I have not seen the Fatal Error since but just thought I’d give you a heads up anyways.
- Site Health: Submitted via form
- No errors
- I have no further log errors.
Forum: Plugins
In reply to: [Site Kit by Google - Analytics, Search Console, AdSense, Speed] OptimizeThank you Adam. I already enabled Optimize and Anti-Flicker on my site. I am still not clear *which* version of Optimize SiteKit installs. It seems like it’s the asynchronous one, am I right? I can’t tell how it’s being loaded right now.
I have an Optimize Experiment running on just one page via “Page targeting”. However with the current SiteKit installation Optimize and Anti-Flicker are loading on *all* pages via the site’s <head>. I guess I am answering my own question here but I was looking for a way to load optimize and anti-flicker on just that one page that has an experiment, I guess I will need to create a custom <head> for that page rather than using SiteKit.
Forum: Developing with WordPress
In reply to: theme.json and font families in WP 5.9This was really tricky. You need to use the font slug to reference the custom CSS variable.
You need to add your 2 fonts to theme.json as follows. Notice the SLUG names and how they connect later.
"typography": { "fontFamilies": [ { "fontFamily": "\"Gotham\", sans-serif", "slug": "heading", "name": "Gotham (Display)", "fontFace": [ ... ] }, { "fontFamily": "\"Karla\", serif", "slug": "body", "name": "Karla (Body)", "fontFace": [ { "fontFamily": "Karla", "fontWeight": "200 900", "fontStyle": "normal", "fontStretch": "normal", "src": [ "file:./assets/fonts/Karla-VariableFont_wght.ttf" ] }, { "fontFamily": "Source Serif Pro", "fontWeight": "200 900", "fontStyle": "italic", "fontStretch": "normal", "src": [ "file:./assets/fonts/source-serif-pro/SourceSerif4Variable-Italic.ttf.woff2" ] } ] } ] }And then under the styles property is where you apply them. Notice the SLUG is what is used to create the custom CSS property:
"styles": { "elements": { "h1": { "typography": { "fontFamily": "var(--wp--preset--font-family--heading)", "fontWeight": "300", "lineHeight": "var(--wp--custom--typography--line-height--tiny)", "fontSize": "var(--wp--custom--typography--font-size--colossal)" } }, "h2": { "typography": { "fontFamily": "var(--wp--preset--font-family--heading)", "fontWeight": "300", "lineHeight": "var(--wp--custom--typography--line-height--small)", "fontSize": "var(--wp--custom--typography--font-size--gigantic)" } }, "h3": { "typography": { "fontFamily": "var(--wp--preset--font-family--heading)", "fontWeight": "300", "lineHeight": "var(--wp--custom--typography--line-height--tiny)", "fontSize": "var(--wp--custom--typography--font-size--huge)" } }, "h4": { "typography": { "fontFamily": "var(--wp--preset--font-family--heading)", "fontWeight": "300", "lineHeight": "var(--wp--custom--typography--line-height--tiny)", "fontSize": "var(--wp--preset--font-size--x-large)" } }, "h5": { "typography": { "fontFamily": "var(--wp--preset--font-family--heading)", "fontWeight": "700", "textTransform": "uppercase", "lineHeight": "var(--wp--custom--typography--line-height--normal)", "fontSize": "var(--wp--preset--font-size--medium)" } }, "h6": { "typography": { "fontFamily": "var(--wp--preset--font-family--heading)", "fontWeight": "400", "textTransform": "uppercase", "lineHeight": "var(--wp--custom--typography--line-height--normal)", "fontSize": "var(--wp--preset--font-size--medium)" } }, "link": { "color": { "text": "var(--wp--preset--color--foreground)" } } }, "spacing": { "blockGap": "1.5rem" }, "typography": { "fontFamily": "var(<strong>--wp--preset--font-family--body</strong>)", "lineHeight": "var(--wp--custom--typography--line-height--normal)", "fontSize": "var(--wp--preset--font-size--medium)" } }- This reply was modified 2 years, 8 months ago by rima.
I did so already, looking forward to your response…
Fixed it.
Next selector should be:
.archive-pagination .pagination-next aForum: Networking WordPress
In reply to: Multisite wp-admin URL ProblemI answered my own question. In network admin, Settings => Domain Admin, simply deselect “Redirect administration pages to site’s original domain (remote login disabled if this redirect is disabled)”. Duh!
Forum: Fixing WordPress
In reply to: Sexy Bookmarks appears twiceThe problem is that this Plugin automatically inserted some code into your single.php Theme file. In the Plugin settings for Shareaholic, simply set Menu Location => Manual Mode, this is located all the way at the bottom of the settings page. This should fix the double display of the Sexy Bookmarks plugin.