conradish

Came looking for the same. This code worked perfectly. Thank you.

@shea

While I do wish you’d provided this feedback in a more constructive form, it’s very helpful to discover the sorts of sample snippets that users would like to see. I might take another look at what we currently provide by default and see if I can add the CSS/JS ones back in a way that wouldn’t increase confusion between the different features.

So I don’t think the feedback here is unconstructive at all. It’s helped point out something that is missing from the free version that users like myself and the OP used to use. It is also confusing that the only reference to using CSS while using the plugin is to upgrade to Pro. Leaving the original example css files would have kept me as a user, but I’m not already enjoying a different snippets plugin that comes with much more in the free version (including comprehensive CSS snippets that allow you to choose where the CSS is located).

The way you have changed your free plugin definitely makes it seem like Pro is required for CSS snippets, but I think that is likely your intention, and only you will know whether that pays off in the long run.

So it seems like this is a game of smoke and mirrors

@shea. The example css php snippet you show were exactly the ones that came as examples with the original free code snippets plugin, that have now been removed. Here is the snippet that used to come with a Code snippet until around a year ago, to instruct the user:

add_action( 'wp_head', function () { ?>
<style>

	/* write your CSS code here */

</style>
<?php } );

this snippet had the description:

This is an example snippet for demonstrating how to add custom CSS code to your website.

You can remove it, or edit it to add your own content.

This snippet is now gone. The plugin actively made it easy to add CSS, and the snippet came with the clone option below. All you had to do was clone and add PURE CSS only. That’s all that was needed Clone and Add CSS. No quicker that your pro version I’m sure! These snippets were tagged as CSS but have been REMOVED from the free version.

All the new version is doing is doing this behind the scenes, it requires no fewer clicks, and makes it seem to the user that they need to upgrade to pro in order to add CSS.

The fact that the new version no longer includes these pre-tagged CSS snippets, makes it worse for the user. Even your suggestion here that you cannot add “PURE CSS” is disingenuous. Any CSS code added was pure! Likely your new CSS inclusion in pro, is just similar code, but hidden from the user by one layer, and an unnecessary UI, that is all.

As someone who has used code snippets for several years, this change, couple with the prompt to upgrade to pro for CSS snippets. is not appreciated. and it has caused me to stop using code snippets. I now use an alternative snippet plugin, which actually seems nicer in some areas, although I was very happy with your old free plugin for several years.

@brian

You just seem to be repeating Shea’s line which is odd, are you commented with this plugin somehow?? I guess you haven’t been using very long if you haven’t noticed the missing CSS snippets

I’m not confused, the example CSS snippets which used to be included in Code snippets no longer are. You’re not going to convince me and other users that that we were dreaming it all up!, especially as so many users are still running code snippets 2.14.x and using CSS snippets using the clone feature straight out of the box.

• This reply was modified 1 year, 10 months ago by conradish.

No, none of the versions I have installed are in anyway modified or customized. As I said, they are all out of the box, and installed directly through the worpress installations “add new plugin” method that automatically links to the wordpress plugin repositories from keywords. every time.

I think you should be far less trusting of the developer here, in the link you supplied he says:

“We’re committed to ensure that the functionality of the free version of Code Snippets only improves over time, and never decreases.”

This is simply not true.

I don’t mind freemium as long as your original free plugin isn’t later demoted to force paid for pro options. Especially if this is part of an upgrade path, and without informing current users. The plugin author here is not being honest about these changes. I can longer trust or use this plugin due to that. If you’re going to try to ramp up your sales of pro, at least be honest with it.

I don’t need to download 2.14.0 I’m already running it! and another site running 2.14.3, and another running 2.14.1 (All three of which come with fully functional CSS snippets). I wouldn’t have been using if it didn’t run CSS snippets out of the box.

And that’s clearly what others are seeing. And why are you going to this much trouble to try and prove the opposite of what we are experiencing and what is obviously true? and not be in any way more inquiring and intrigued about this?. Why would we all want to make up such a thing about something so specific and demonstrable! As soon as I instaled on a new site it was “Oh, Well that doesn’t work like it used to!” Immediately uninstalled and won’t be using for future projects anymore.

Anyway, here’s my screenshot of my 2.14.0 in actual use on a live site, plugin was installed November 2020:

Functions perfectly for CSS and comes with CSS examples, tagged and everything, ready for cloning (these come with the fresh install). The site runs multiple CSS snippets perfectly. I won’t be upgrading though!! And wont be using this plugin for future sites. Extinction by monetization is the new plugin business model for this one I think. Sad, I often donate to plugins like this after I realize I’ve been using them for a while, but obviously not in this case.

So Brian, I’m afraid that is completely incorrect. In fact I have a site running code snippets 2.14.0. CSS is completely included and fully functional. And that’s the very reason I am here, because it no longer is. Sure it might have been added to pro after being removed from the free version. But it absolutely existed not that long ago. IF you look at the stats you’ll see plenty of people still using 2.14!! ??

What’s very strange is the attack at people stating this. The attack itself is odd. Calling people rude etc etc, and the developer too. Hmmm something is not right here at all.

So I’ve just uninstalled code snippets on a site after using for several years.

It now no longer has CSS snippets, and suggests upgradng to pro in order to use them. I’ve switched to another snippet plugin, which is used by more users now.

I’m not sure why people here are saying the free one hasn’t changed when it so clearly has.

I don’t understand this. Please could this be clarified. I’ve previously used Code Snippets extensively. Just installed in on a fresh site and it wants me to upgrade to pro to add css snippets. CSS snippets was previously included for free., it now isn’t. The plugin author seems to be saying otherwise. What is going on?

For me CSS is a greyed out option whereas previously it was simply usable.

Was about to leave a review (this is not an awful attitude imo) but feel I now need clarification. Do I need to upgrade to pro for CSS snippets? And will I experience what OP has experiences when upgrading older sites. How come plugin author is saying nothing has changed when it clearly has?

You could try to get round this by using the “ignore keywords” setting in flying pages and adding all the other links. Maybe.

Oh Ok.
Managed to resolve issue in the end using Elementor columns to restrict width in mobile.
Thanks anyway.

Hi, having the same issue here. Could I ask what the resolution was?

The thing is, this should not be a feature request imho. It is required.

Visitors need to know an event is no longer available straight away. All event organisers want old event urls to exist for SEO and archive reasons, but there needs to be a simple way to show it has expired, even if just on the event page itself.

This should be an easy and necessary thing to add asap.

It doesn’t sound like an error. JFK wants to be able to hide information in expired events. This is necessary. Similarly I would like the option to clearly state an event is expired somewhere on the event page Ideally this would be a normal style elementor text element which only displays when an event is expired. A conditional toggle would easily resolve this.

OR you could add ” do not show for expired events”/”only show for expired events” in your settings pages. You could add an “expired events” setting page for this.

Like JFK’s request, imho, this should be part of the system to have expired/upcoming conditional visibility toggle on all MEC elements.

Already reviewed it positively a month ago, but updated that review, and waded in on a recent one star review that was just rude. Please stick with it. Simple, complete, and well made plugins like this are what WordPress should always be about.

Just to wade in here for anyone who likes to check the one star reviews (I know i do) A one star review for this seems insane.

It’s a really straightforward plugin that isn’t shouting about how well made it is. If you want or need a “click and collect” system integrated into your normal woocommerce flow this is a perfect plugin imho.

I have no idea what @barricademan is struggling with. For me, in a real world situation, this plugin is missing nothing. And whatever blended header issue he has, certainly isn’t seen this end. The plugin was quick and easy to setup. Click and Collect orders are SOOO easy to manage with this, email templates easy to create, and the plugin even has a nifty area for setting up times of day for pickup in a really well organised way. For the customer the emails they receive are sent at exactly the right times in the process and are easy to understand and provide all the information they require. All in a single click in the order queue. I literally can’t think of anything the pluigin is missing.

I notice @barricademan has posted only one review in 13 years. This maybe isn’t the best or most useful way to becoming a helpful part of the community.

P.s. I’m no shill or in any way connected to Zorem, or this plugin. Feel free to check my post history. I just don’t like seeing bad press for a plugin that I know is well made, is being used everyday, and is well supported by responsive developers.