Customized Structured Data

The version is under development, soon available for us!

I’m testing on live and works good. After you update to dev 3.3.0 you can’t go back because a database update.

Only small problem on dev version are some post meta description you have to save them twice. But that s all.

I m using with wpml, and google loves to crawl tsf Sitemaps ????????????.
Also tsf is faster then previous stable version! And with 800 new tweaks! Sybre is doing a good job.

Forum moderators, before you close this topic: This isn’t about our Premium services per se. But, more about our architecture working with plugin versioning and releasing them into the wild, regardless of it being paid or not. All our support channels are open because all our code (aside from our side’s SaaS API) is FOSS.

Hi Daniel,

I must apologize for the confusion and frustration! The filter provided there isn’t released yet.

The reason your drop-in replacement for Articles didn’t work as intended is that it relies on a new meta-saving callback from the core framework, named \TSF_Extension_Manager\InpostGUI::is_state_safe(). This method doesn’t exist in TSFEM v2.0.4 or earlier, so saving will fail.

Our extension-documentation pages are generated automatically from the plugin files. For Articles, it’s obtained from this markdown file.

Alas, because I don’t have the resources to maintain this asynchronously, I publish them as-is on my networks, with an asterisk dubbed Release date: TBA. I know I could’ve handled this better by adding such annotation at the filter. But, I didn’t think our users were that quick to catch on; this is where our high standards in privacy bite us.

Nevertheless, I’m still working hard on the TSF v3.3 update, which incorporates some changes incompatible with the current version of the Extension Manager.

TSF v3.3 should be in beta by the end of this week. We’ll be testing it live on all websites managed by our team to learn how Google and Bing respond. Moreover, I’m going to freeze the API at beta. From there I can safely touch up TSFEM v2.1.0 (or v2.0.5, TBT), and release that (hopefully) within two weeks from now.

As a full disclaimer, there was a new planned extension (named Cord), but its functionality is being superseded by Google’s Sitekit plugin, as such, I scraped it. So, there won’t be a new extension this release.

TSF v3.3 will be the last major release that is this massive (as Antonio pointed out: over 800 notable changes). It took a long time to change our API to become more consistent, reliable, and allow for more features. Finally, I can say I’m happy with my plugin: v3.3 opens many doors for new extensions that’ll keep working reliably for years to come.

I hope this explains the lot and relieves some of that pain you’ve experienced!

P.S. I was able to match your www.remarpro.com username in our records. To apologize for this confusion, I doubled up the number of connections ?? Cheers!

@onestatero Can you replicate the description not saving consistently? If so, could you email me the details? Thanks!

Dear Sybre,

thank you for your response and taking the time to write in such detail.

I understand und appreciate all the hard work that goes on “behind the scenes” and your aspirations regarding code architecture and software quality. It really makes a difference since there are so many bad written or half-baked plugins out there.

Alright, looking forward to the upcoming releases then. Sounds like this will be a big leap into the future ??

Oh, and thanks a lot for adding some extra candy for us with the doubled up connections. Really nice! ??

Keep up the good work

• This reply was modified 5 years, 4 months ago by zitrusblau. Reason: typo

Hi Sybre.

I ll write you an email this evening.
Now after new update ( this afeternoom- my time – I ve downloaded new code from git) it’s all seams to be ok!