Matthew Taylor

WordPress version 6.4.3
Active theme: Binoid Child Theme 2024 (version 1.3)
Current plugin: GTM4WP – A Google Tag Manager (GTM) plugin for WordPress (version 1.20.2)
PHP version 8.2.14

Error Details
=============
An error of type E_ERROR was caused in line 107 of the file /nas/content/live/shop2binoidcbd/wp-content/plugins/duracelltomi-google-tag-manager/admin/admin-tab-basicdata.php. Error message: Uncaught Error: Undefined constant “GTM4WP_OPTION_INCLUDE_VISITOR_IP_HEADER” in /nas/content/live/shop2binoidcbd/wp-content/plugins/duracelltomi-google-tag-manager/admin/admin-tab-basicdata.php:107
Stack trace:
#0 /nas/content/live/shop2binoidcbd/wp-content/plugins/duracelltomi-google-tag-manager/admin/admin.php(132): require_once()
#1 /nas/content/live/shop2binoidcbd/wp-content/plugins/duracelltomi-google-tag-manager/duracelltomi-google-tag-manager-for-wordpress.php(47): require_once(‘/nas/content/li…’)
#2 /nas/content/live/shop2binoidcbd/wp-includes/class-wp-hook.php(324): gtm4wp_init(”)
#3 /nas/content/live/shop2binoidcbd/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#4 /nas/content/live/shop2binoidcbd/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#5 /nas/content/live/shop2binoidcbd/wp-settings.php(506): do_action(‘plugins_loaded’)
#6 /nas/content/live/shop2binoidcbd/wp-config.php(143): require_once(‘/nas/content/li…’)
#7 /nas/content/live/shop2binoidcbd/wp-load.php(50): require_once(‘/nas/content/li…’)
#8 /nas/content/live/shop2binoidcbd/wp-admin/admin-ajax.php(22): require_once(‘/nas/content/li…’)
#9 {main}
  thrown

This specific answer is helpful, but the plugin features listed includes: “Retain query strings across redirects” that seems to covers this situation.

Is there a list of free vs pro features?
I checked https://www.webfactoryltd.com/wordpress-products/ and https://wp301redirects.com/

@klynam

I’m not a developer, I’m a user and designer and the only ones with voices in the WP core development are programmers.

I’m a designer.. There are lots of places where developers are working on these issues and actively seek outside opinions from non-programmers.

Since you’re a mod, I have to be careful with MY replies to avoid getting banned, or having my threads closed or removed entirely.

It’s hard to have a good productive discussion about the issues with you taking personal offense and proclaiming what a victim you are. You are claiming there are walls where there are none.
I’ve seem Esmi around quite a bit. Always very helpful. And patient. Oh my.. so very patient. As is evident in this thread.

At a broader level, this is simply good interface design protocol, but yes it does take more work – which of course is why it seldom happens as it really should.

Good interface design is what the developers were working on. I disagree with some of their changes.. but they had design parameters and goals in mind you have not taken the time to look up.

@lonchbox I agree on that point. The Links post type hasn’t been gone that long. And for those that added it back in via plugin.. What is it labeled as? I looked it over because I thought it WAS the links post type. ‘Custom Link’ would have been a better label. That did waste a bit of my time due to confusion.

The custom post type I made is rather interactive and contains several forms.
The way I was including the PHP files for one of the forms left out a form closing tag. I think through some WordPress magic the form tags from the new form the comment_form() was trying to create was stripped.
I discovered this when I moved the comment form to the top of the page and it worked.

The default css file is the style.css of the theme. It’s a custom theme. I need approvals from my client. We often have trouble getting the style.css to update due to browser caching. So if I make major changes it’s possible we won’t see the same thing. That’s why the version number is the last time the style.css file was changed. It won’t break caching for that file unless it’s been saved by me. I like this solution, because it’s not something I have to remember to remove before going live. It’s not really the kind of thing the will have a performance hit.

I think I found my problem. I wasn’t careful about where I dropped the function into my functions.php file.

It was being put in to the functions file after:
if ( ! function_exists( 'dlab_setup' ) ) :
That means it was being called after the ‘after_setup_theme’ hook. The default inclusion of style.css has already been added to wp_head() and the wp_enqueue_style ends up tacking on another link to the same stylesheet.

A silly mistake. But I’m glad I was able to figure it out.

update: let’s try the correct WP function:

function css_versioning() {
 wp_enqueue_style( 'style-css', get_stylesheet_directory_uri() . '/style.css' , false,filemtime( get_stylesheet_directory() . '/style.css' ), 'all' );
 }
add_action( 'wp_print_styles', 'css_versioning' );

better.. but still 2 entries:

<link rel="stylesheet" id="style-css" href="https://mrtwebdesign.local/ddd/wp-content/themes/dlab/style.css?ver=3.5.1" type="text/css" media="all">
<link rel="stylesheet" id="style-css-css" href="https://mrtwebdesign.local/ddd/wp-content/themes/dlab/style.css?ver=1366413348" type="text/css" media="all">

How do I get down to just the one ‘style.css’ with my version number(not the WordPress version number)?

I looked at the dif’s in Trac. While it may be technically accurate.. I wouldn’t want to sit and have to decode it. I would be looking for a summary not unlike the WordPress 3.3 list of changes.

Vas Pro made another plugin for RSS feeds. Also added spam backlinks to the footer.

I’m a newcomer to WordPress and I find it bizarre that this behaviour is considered ‘OK’. It is obviously a bug. This is old behaviour left over from shoving two different systems together. The situation benwisdom has should not exist. It took a lot of work to figure out why the category system was ‘broken’.