Q-collective

Alright, upgraded now to Ubuntu 22.04 and the theme works as expected. Resolved ??

That’s certainly possible. The server is still running Ubuntu 18.04. I’m currently attempting an upgrade actually. I can see if that fixes it.

That’s great to hear! I’ll work with the workaround for now. Hopefully this thread is useful for others. Thanks for your quick responses ??

Yeah, apparently I had English as the default language in Chrome. When setting it to Dutch, the website loads as expected. But this is of course an issue when people are unaware that they’ve set their website to English as default, and then being unable to switch to Dutch ??

So, a proper solution would be good. A functional cookie seems fine if that is the route to take.

So, this was never resolved, and the issue is getting worse with a few more cancellations. Is there some way to for Paytium to “rebuild” the tally?

Yeah, tried that too. Even binning it. No update.

Thank you for your reply. The payment has been cancelled as per 30-8-2020. But it wasn’t subtracted. So, according to the Paytium progress bar, I still get the donation.

Bump? Is there a workaround perhaps if no support is forthcoming?

That pre-release doesn’t list recurring payments. Is there work this feature at all? Recurring was introduced in the API last May, with the promise that plugin support would come “soon”. This is getting a bit frustrating.

Thanks again for keeping a close eye to this. I can report that the issue remains in 1.0.2. I’ll have a look at your code changes in the morning ??

Thank you for your prompt reply. I’ve added the rule you suggested in the custom CSS file, but without result.

I’ve looked in the main style.css of my theme and couldn’t find a “text-align: left !important;” related to the content in question. I’ve put the content of the style.css on pastebin, if you’d like to give it a look.

If it can’t be resolved by hand, I’ll just wait for an update of the plugin ??

Thank you dear sir ??

Thank you for your reply. Regarding the Dutch translation: that does explain the behaviour of the plugin. And I do hope you can get to custom fields feature some time soon ??

For now I’ll use the Contact Form 7 plugin for people to get in touch and use Awesome Support as the back office ticket system. That’s a good enough workaround for me.

Thank you for your reply. It appears that, for now, we’ll have to stay on 1.17 then ??

Do you know if the 1.x branch still gets updates should compatibility with future upgrades of WordPress break? Or is it abandoned as EOL?

Also, you have activated the cover in settings page, correct? (gotta make sure)

I… did not. That is the obvious thing I completely overlooked.

So yeah, plugin works fine. Sorry to bother.