Jer Clarke
Forum Replies Created
-
Thanks for the reply! FWIW I’d love to see this feature added as an attribute on the shortcode. In that case it wouldn’t have any effect on sites where it results in an unhelpful number, but for sites that just want to show the total number of objects, it would be very helpful.
I looked at the template, and overriding it is a good option, but I always hate to duplicate code like that, in case you changed it in the future.
Looking at the content ofposts-found.php, it seems like another good option would be a filter that affects the$posts_found_countthat gets used in the template. If there was a filter, I could use it to set it to the total count of objects when it’s empty, and get the result I’m looking for.
Without a filter on$posts_found_countI feel the best solution will be to filter the output of the shortcode itself, and use the HTML API to insert the total count when the container is empty, but that still feels very messy.
Thanks again for the reply, and for considering my ideas 🙏🏻Forum: Reviews
In reply to: [Polylang] Free version is useless with block themes?Ok, thank you for pointing out that you do have some kind of solution available. That plugin seems handy for other uses as well, though it does seem like a really unnecessary dependency, considering that you already have the feature available and coded in the Pro version.
I was trying to set up Polylang based on the documentation here: https://polylang.pro/documentation/support/guides/the-language-switcher/
If installing your other plugin is the solution, you should add it to the documentation as well as the plugin description.
Personally, I started coding a custom block just to show the output of
pll_the_languages()so I could test out the plugin (and practice making blocks).All that said, I’d really ask you to consider: Who is it that is using FSE and the default themes at this point? Is it big industrial clients for whom the Pro license fee is nothing? Is it professionals building sites for clients?
It really seems to me that FSE is currently disproportionately used by beginner users and/or advanced users building low-stakes low-profit sites. These are people who are going to be looking for free solutions, at least at first, and something they can’t try without paying is going to be a non-starter. Why make it so hard for them, with complex workarounds involving extra plugins that make the whole interface more confusing? For a new users using FSE because it’s default, telling them to ALSO learn the old menus and widgets system is really upside-down.
Just make FSE work out of the box, but with limitations that make you want to get the paid version, like you do for classic themes. The biggest strength of Polylang compared to WPML, for a newbie, is that you can use it for free. I’m sure this model has helped you a lot over the years, but it’s not going to work if newbies using FSE are kept out.
Your reply makes it sound like you don’t think you have a lot of FSE users, well yeah of course not. With the way the freemium system currently dissuades beginner FSE users from ever trying Polylang, your FSE features are never going to get used at all 🤷🏻♀️
Just tested and it’s working properly now, thanks!
Wow, incredible that you fixed it already!
Just tested it and Safari is working again, uploading as normal (Safari 26.0.1 on macOS 15.7.1.
Though for some reason I’m getting a new bug: On Chrome every upload is showing up twice, seemingly with the original upload and then the Cimo version:

As you can see, the most recent image is there twice, first the original JPG image, then the optimized WebP.
Really strange! Is this something specific to me?
I also tried it in an empty Chrome “profile” with no extensions installed, and using a site with almost nothing installed, and got the same result.
+1000 This is an incredible plugin… as long as you have 100% control over all authors on your site!
Our site has hundreds/thousands of users who might upload something. I would love to use Cimo but as long as the Safari outcome is that it’s just broken, I can’t even think about installing it.
The solution needs to be that if it’s not going to work, it’s simply disabled and the upload happens as it would normally. Maybe with a warning that it’s not optimized, but not with anything that blocks uploads from happening normally.
Please! It’s such a great idea, but for now a lot of sites won’t be able to enjoy it.
Thanks Shawn! I’ll close this ticket and look forward to removing my hotfix when the next version comes out. Always appreciate your team 🙏🏻
Update: I pushed that change to my live site and everything still seems to work. It definitely silenced the warning.
Awesome work, fixed it for me! Thanks for sending the patch 🙏🏻
Muchas gracias 🙏🏻
Bumping so hopefully this doesn’t get closed and force me to write it again. This code has been working fine on my site after the transition.
Ok, after more looking, it seems like I might be getting bitten by the limit of 25 sites per Google account. What an annoying mess! Why wouldn’t the limit of API tokens match the limit of properties on the account?!?
Thanks for all your work, I’ll have to try to address this with the solutions you propose here and if that doesn’t work, come back.
Sadly I am experiencing this too.
Like Alin said, no data is actually lost, it works like the old Google Analyticator plugin where the tracker continues being output with the correct property ID until you manually reset, so if you see data missing, you’re either not looking in the right place, or it’s something else. Thank god for this fallback!
But yeah, like Danniee I’m finding that whenever I go back to a site after awhile, it’s logged out. I wouldn’t say it’s every day, but I configured 50 sites a few months ago, and every single one of them that I’m visiting now is disconnected, and the ones I visit regularly I’ve had to reconnect several times now.
There’s no error in Errors & Details, just the generic screens:

(as a sidenote, it might be good to add a notice at this point about the tracker still being active. A message saying “The API is disconnected, but we’re still logging data to [XYZ profile]” would go a long way to assuaging people’s stress. I suspect most people don’t care nearly as much about the dashboard reports as they do about the tracker being in place.)

Here’s a gist with the redacted contents of the Plugin Settings tab: https://gist.github.com/jerclarke/3ef221cca4e8f4986924b6c532205cb0
Thanks for any help on this Alin. Have you not noticed it happening on your sites?
Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Completely bypass AkismetHi Steph!
FWIW I also need this for my acceptance testing with Codeception. All in all I’d like to keep Akismet enabled, but don’t want it affecting my comments testing. A dedicated filter I could rely on would be a huge help.(ideally, it would be a filter that could be added on
init, rather than requiring an mu-plugin or whatever. The filter you gave needs to be run super early which is a big inconvenience)- This reply was modified 3 years, 3 months ago by Jer Clarke.
Hi, thank you for that.
I have another similar report, so I’ll put it here rather than starting a new thread:
From /powerpress/views/settings_tab_appearance.php on line 32:
<input type="text" id="subscribe_page_link_href" class="pp-settings-text-input" value="<?php echo esc_attr($FeedSettings['subscribe_page_link_href']); ?>" name="Feed[subscribe_page_link_href]" placeholder="Subscribe URL"<?php echo (!empty($FeedSettings['subscribe_page_link_id'])?'':' disabled'); ?> />This generates the following error:
PHP Notice: Undefined index: subscribe_page_link_href in /.../wp-content/plugins/powerpress/views/settings_tab_appearance.php on line 32The reason is obvious, the code accesses
subscribe_page_link_hrefwithout checking it exists, unlikesubscribe_page_link_idwhich it uses on the same line, but only after checking!emptyThe state of the page, for me is that I don’t have any settings set up, so I guess it’s empty in that case:

You know what, I got it working with the help of the Thyngster docs!
With this hook I can insert all my normal parameters, including my “Screen Type” one, which has a post-amp one for AMP!
add_action('aiwp_analytics_amp_config', array($this, 'action_aiwp_analytics_amp_config_to_insert_global_parameters'));…
public function action_aiwp_analytics_amp_config_to_insert_global_parameters(AIWP_Tracking_GA4_AMP $aiwp_amp) { $config = $aiwp_amp->get(); $parameters = $this->get_all_global_parameter_values(); foreach ($parameters AS $parameter => $value) { $config['extraUrlParams']["event__str_$parameter"] = $value; } $aiwp_amp->set($config); return; }Beautiful work on this plugin! Everything was ready to go once I parsed the somewhat-confusing docs from Thyngster!
Now I just need to figure out how/if I can have a second tracker in there!
- This reply was modified 3 years, 6 months ago by Jer Clarke.