veex2

I understand the context of the decision and the intent. This doesn’t change that it misses the mark on how your team classifies commercial entities. The assumption is that every month everyone classed with a catalog only or a minor ecommerce platform is rolling in cash, as we’re in an actual slowdown through 2024 many aren’t, this move is likely inspired by that as well.

The issue is that assumption isn’t actually based in reality. This especially stands out for a site that I had impacted by this, I produced the site on my own out of pocket to make my life easier at work, I end up on a loss with it and now even the baseline for stats is beyond a stretch for something that was a convenience. While it was nice having Jetpack stats, the only thing it’s done is alienate me and make me skeptical of what might be taken away next. Your team might view it as what’s $100 a year for this feature? Well since it’s out of my pocket, it’s $100 for something that I will be able to live without as it’s not an essential product.

Worse is that currently for those that opt into the new stats unaware of what’s about to happen are stuck with no option to opt out as the slider to disable it is greyed out. So not only are their stats useless because of the prompt to pay, but they can’t even get rid of it. If the team can’t understand how that’s bad, I don’t know how to help you. Using a bypass was the only way to easily disable it at the time.

As a final note, for people with hosting plans like Jetpack Professional stats aren’t included and considered an upgrade, I can only imagine that as time goes on the team will continue to prune off included items. Generally that’s how this process goes, chip it away.

I wish your team the best with it but it’s not going to be for everyone and hopefully your team actually understands why. I’ve tried to express this in the beta before, I’ve been rejected countless times for consideration into the free program because apparently your team thinks I’m making millions and just being stubborn, I’m not, and many others aren’t as well.

As noted in a related post, this falls back to the permissions you granted to Jetpack, unless all syndicated posts are using your username you need to enable sharing permissions for all users otherwise Jetpack follows your directions and ignores any user that isn’t your account.

Disabling the sharing and enabling it again gives the chance to configure the permissions yet again. It sounds like that’s what most users have been encountering and it’s not the fault of Feedwordpress it’s just poor user configuration.

Indeed, I’m just basing this on syndication of about 300-400 posts a day from my feeds to my Twitter and Facebook channels and I haven’t had an issue on it. In my case I’m just using Jetpack configured with keys to my accounts using global permissions for posting rights, if you set Jetpack up with exclusive publicize rights to just your posts then it’s only going to do your posts because those feeds aren’t you, that’s why it asks as such and it’s a pretty common oversight.

Not sure what that issue would be, I’ve been using it for quite a few years and my theme still has sharing icons visible in posts from Jetpack, if you’re using another plug-in that might have its own compatibility issues.

Publicize also works to get my feed items out, I’ve had issues before but not lately. Again it might depend on what you’re using and how that’s configured for sharing.

Could be a theme, configuration, other plug-in issues and so on. Without details it’s probably pretty hard for anyone to narrow down possible causes especially if it’s an isolated user case.

Radgeek actually has a plug-in for this listed on the FWP website, it’s called “FWP+: Limit size of posts” it should do exactly what you’re looking for.

If the author of faf does decide to return to update the plug-in then yes they could solve it in probably a better way, for now those curious about getting it operational without altering feedwordpress itself will have to manually edit those fields.

Personally I’d rather have Feedwordpress operating as it should and edit faf errors as they come up vs compromising Feedwordpress.

Tinkered around with this just to see what line 464 was about.

The $context lines are clashing there and again in 183 and 184 in faf’s feedwordpress_advanced_filters.php file, I changed faf’s $context references there to context1 instead and was able to get the plug-in to work again,

Altered 183 and 184 from faf

	  	 		$av_filters[$context1][$name] = array("filter_text" => $desc, "filter_function" => $c); 
				$av_filters[$context1][$name]["filter_controls"] = $c::getControls();

Altered 464 from faf

  	        switch($page->context1)

Haven’t had an issue yet but it should help anyone hoping to get the options page working again.

Fixed it! ?? thank you so much

You can see a sample of it here

https://consequencesofexchange.com/testbox/newstuff-test-002/

Content missing using their sample code of

[table]Year,Make,Model,Length
1997,Ford,E350,2.34
2000,Mercury,Cougar,2.38[/table]

I can roll back for now, just wanted to be sure it got noted though. Thanks for the quick update! ??