eagerbob

Ah! found it.

It is in the Customiser. Not a place I visit very often, but glad I did.

Anyway, this is solved.

Thanks!

Ok @antoiub,

Thanks for your quick reply. In Slider Revolution, I set the Global> “Enable Google Fonts Download settings” to Cache Fonts Local

And in Complainz I set the “will you self-host the Google fonts” to no. That solved the issue.

Interestingly, I do not use Google Fonts in my sliders. It is SR itself that uses Google fonts (Roboto, Inter) , presumably for its own interface? Which is far from ideal when it clashes with the GPDR.

I do use Google Fonts on the site, but I can easliy host them on the webserver which is a better option anyway.

Thanks again!

• This reply was modified 1 month ago by eagerbob.

Still the same error. Same browser, certainly no 24 hours between receiving the key and trying to register. Most annoying thing is the modal screen that goes over your plugin dashboard all the time…

Thanks again,

I’ve got facet-wp working so that is good.

Is there really a parent/child relationship between pages, or is it an arbitrary relation solely to accomplish the ordering? If it’s arbitrary, why not be really arbitrary and order by menu_order? This is only available for pages, not posts. 

The “jobs” started out as pages indeed with a parent/child relation but I changed that to posts to match the “vacatures”, which are posts.

The “vacatures” posts come from a CRM and add a whole list of custom taxonomies to the posts. They are not visible from the “edit post” page but they are visible from the “quick edit” page, strangely enough. So by adding these taxonomies terms to the “jobs” category posts facet-wp can work its magic across the two categories.

I will try the parent-child varation for the taxonomies, see what that does. Will also make it easier for the visitor to drill down to what he is looking for.

It is a bit of a puzzle to get it all working but we are getting there. Thanks for the tips.

• This reply was modified 1 year, 1 month ago by eagerbob.

If it is:

.intro p {}

that means all paragraphs within an element (like div or span or whatever) with class “intro”. Like <div class="intro> p </div>

Whereas

p.intro {}

means paragraph with class “intro”, like: p class="intro"

• This reply was modified 1 year, 1 month ago by eagerbob.

OK thanks. I figured that WP would run the first query first, then the next one. Before trying this I had two seperate queries and display them after each other. Works fine, but I want to filter the results with facet-wp. This requires/uses a query on the page. Not sure if facet-wp can search filter across categories, have to check that.

Re-ordering the query results results is too complex. I look into the orderby options. Maybe I can make the “jobs” the child and “vacatures” the parent. See is I can order by parent (not sure how that would work)

What I would prefer to do is to give them both the same category. They are both “jobs” or “vacancies” the difference being that posts in one category is managed from outside, the other is created from within WordPress. But since they have different single post templates they cannot be in the same category.

I think I do some testing.

Thanks again

Could be something like:

.post-template-single-regularpost p {color:red}

This means that all paragraphs on pages that use that template (and thus get that body class) will be red. If you want only the paragraph in the product_regpost div to be red you could use something like:

.post-template-single-regularpost .product_regpost p {color:red}

hope that helps

• This reply was modified 1 year, 1 month ago by eagerbob.
• This reply was modified 1 year, 1 month ago by eagerbob.

You should try deactivating all plugins and switching to a default Twenty* theme.

OK found it. It was a plugin “redirection” that had been installed by someone at the client. Never noticed it because it was not something I expect anyone to do.

Lesson is to *never* give admin rights to clients managing their own sites when it is not absolutely necessary. Which it almost never is…

Thanks!

• This reply was modified 1 year, 1 month ago by eagerbob.

Backups you will find, normally, in the dashboard/control panel of your hosting provider of your website. *If* there are daily or weekly backups there is a possibility to restore the site to a certain point in time. If you do not have access to the control panel, ask them. Or your developer.

For FTP access you use an FTP program. If you do not know what that is, you probably should not bother. Ask your developer.

Have you tried the settings in Rank Math and checked “strip category base” ?

https://boomdevs.com/easy-ways-to-remove-category-from-wordpress-url/

You will need to rollback to a backup you made before you upgraded the plugins. If you do not have or made a backup before updating, ask your developer or hosting provider.

Alternatively, you can access the site through FTP and see if the functions file is indeed missing, and put it back form a local copy of your theme.

• This reply was modified 1 year, 1 month ago by eagerbob.

Elementor is a visual website builder that lets you build a website with basic features. PRO is a series of add-ons that offers fancy features that you may or may not need, depending on what you are trying to achieve. Elementor PRO is the suite of add-ons that are offered by Elementor. It may be good to know that there are more add-ons available outside Elementor Pro. Some free, some paid. If you google for “elementor add-ons” you will find plenty. Worth checking out before you buy PRO. Another option is to buy a theme that already has some PRO add-ons included with the theme.

• This reply was modified 1 year, 1 month ago by eagerbob.

Yes, that’s it. No parenthesis.

Thanks!

Ok I changed the code following the information on developer.wordpress but I kept getting errors. Like a “unmatched “}” at the end of my file. Which seems easy to fix but wasn’t.

I “Solved” it by removing the widgets alltogether. It was a Flickr and a twitter widget, both are not used.

Thanks

OK Thanks Hiren for your quick response.

Unfortunately I still get an error:

`Fatal error: Uncaught ArgumentCountError: Too few arguments to function WP_Widget::__construct(), 0 passed in /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-widget-factory.php on line 62 and at least 2 expected in /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-widget.php:163 Stack trace: #0 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-widget-factory.php(62): WP_Widget->__construct() #1 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/widgets.php(115): WP_Widget_Factory->register(‘zilla_FLICKR_Wi…’) #2 /Users/eagerbob/Local Sites/cinetone/app/public/wp-content/themes/cinetone/includes/widgets/widget-flickr.php(21): register_widget(‘zilla_FLICKR_Wi…’) #3 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-hook.php(308): zilla_flickr_widgets(”) #4 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #5 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #6 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/widgets.php(1854): do_action(‘widgets_init’) #7 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-hook.php(308): wp_widgets_init(”) #8 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #9 /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #10 /Users/eagerbob/Local Sites/cinetone/app/public/wp-settings.php(617): do_action(‘init’) #11 /Users/eagerbob/Local Sites/cinetone/app/public/wp-config.php(91): require_once(‘/Users/eagerbob’) #12 /Users/eagerbob/Local Sites/cinetone/app/public/wp-load.php(50): require_once(‘/Users/eagerbob’) #13 /Users/eagerbob/Local Sites/cinetone/app/public/wp-admin/admin.php(34): require_once(‘/Users/eagerbob’) #14 /Users/eagerbob/Local Sites/cinetone/app/public/wp-admin/index.php(10): require_once(‘/Users/eagerbob’) #15 {main} thrown in /Users/eagerbob/Local Sites/cinetone/app/public/wp-includes/class-wp-widget.php on line 163′

Seems I’ll have to dive a bit deeper for this.

Found some info on Stackexchange: https://wordpress.stackexchange.com/questions/383777/too-few-arguments-to-function-wp-widget-construct/383778#383778

Thanks again

• This reply was modified 1 year, 12 months ago by eagerbob. Reason: redacted code