Shady Sharaf

Ah, got it, makes sense.

Nice to know about the background sync being on the roadmap.

And regarding the problem, yes, we’re trying to transition to using cli (loco’s though, as it’s more convenient) to ship the POT file with releases, currently we don’t version control translations as it spans across multiple repos, but given the timeout, we might need to start doing that.

Thanks for the prompt reply! Closing down.

Well, a filter can expose more information than what specific use cases need, callback can always take what they need and listen for less callback arguments.

For the sake for unknown use cases, I’d probably add back that domain argument to minimize the risk and make it more user friendly.

Thanks for working on this, Tim.

This does seem like it should do the trick! We have the update scheduled to be done next week, so will report back when that happens.

I very much appreciate the prompt response and actions! And sorry for the late reply.

That’s a private theme that uses that code, but you can simulate that by having different path / file names between generation and page load.

And for following conventions, a non-default option to satisfy a growing subset of users doesn’t seem too bad to me. But yeah, hooks and maybe a guide would work as well.

Thanks for adding the hooks in advance!

So, WP does provide ways to override the path to where you can look, which is what I used in my gist. It’s the generation that’s broken, but I’ve not had to use WP’s native tooling to generate files, been always using Loco! (thanks for advocating for users with different use cases on core issues btw!)

And, no, fixing the relative path would not work on its own, my specific issue with loco at this point is being able to control the generation process so I can combine all strings into one JSON file ( and also control its naming ). So adding hooks around that in loco should be fine for me.

And _maybe_ if loco can support that natively (option to specify a single output JSON file for a specific bundle) it would be helpful to large segments of users going forward. But that’s a bit extra.

Thanks for reporting, and confirming the fix ??

/five!

This bug affected any custom taxonomy registered by plugins, which has been identified, fixed, and should be released in the next update, .

It did not affect existing data in anyway, just the label of the taxonomy, so in most situations, you would be able to see an empty spot where taxonomy name should have been.

Hi Tevya,

There has been activity on this GitHub issue which basically does what @fjarret just mentioned, the integration with Akismet, and logging spam comments properly.

Once code is approved, it’ll be merged with the next update for Stream.

/five!

Thank you!

I’ve checked the last time and couldn’t either reproduce nor grasp the possible reason for this, update via FTP, and make sure you deactivate/activate the plugin to install any required DB updates, and lets see if that happens again, We’ll certainly work with you then to work it out if it still persist.

/five!

Great to know you’ve fixed the original issue you were having, and this seems like Stream wasn’t able to handle the errornous install attempt, not at all a compatibility issue with Woocommerce.

/five!

Hi @tiagogoncalves,

I’ve just tried to reproduce your error but couldn’t using Stream 1.4.4 and updating WooCommerce to the latest version, it happened seamlessly without errors.

From what i’m seeing in your log, the update didn’t really happened, and Stream would probably have nothing to do with that since it hooks AFTER the plugin has been actually updated. Note:
> Could not remove the old plugin
> Plugin update failed

If you can fix that, you’d probably be fine working with Stream afterwords.

@imajworks can you get in touch with shady+support [a.t] x-team .com so we may help resolve this issue ?

@bernard so you have s2member and TML installed, can you provide steps to reproduce the issue, and possibly a list of plugins that you have installed, so we can have one of our developers look into the matter ?

Thanks