OK, I read no objections against the principles underpinning this implementation, but there are a few things that need fixing.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 25 2020
May 23 2020
May 22 2020
I've had this problem on debian 8,9 and 10
- The $id parameter is supposed to be a string
- A second proposal to transactions
May 21 2020
Changing to hight, since it is a non working advertised feature -- hence a blocking problem .
May 20 2020
In D1279#14068, @machniak wrote:Maybe we should authenticate the user with IMAP instead? As far as I know the protocol spec. does not require authentication, but it recommends it.
Maybe we should authenticate the user with IMAP instead? As far as I know the protocol spec. does not require authentication, but it recommends it.
This driver is not a high prio for us. Patches welcome.
Currently, the calendar uses the database backend:
The new_event method starts in database_driver and it starts _update_recurring. In this _update_recurring there is a calendar_recurrence object that creates Horde_Date_Recurrence on initialization where the problem is. :)
Yes, it using plugins/calendar/drivers/database/database_driver.php.
May 19 2020
Ok, I was testing a different case. However, this case also works with Kolab backend. I assume that you're using the database driver. Is it right?
Any info? :) Is there anything I can help you to resolve this bug ?
May 18 2020
Rebase
- Add Mollie/Stripe tests
- Browser tests, mollie/stripe
- More browser tests, make possible to run both stripe and mollie tests
- Silence more phpstan errors
- Use wallet's payment provider if exists instead of the default provider
- Support: Display auto-payment info
- Log failed payment responses
@bohlender As you can see here I use btn-warning for the Subscribe/Unsubscribe button, which makes the button orange. I found that yellow didn't work well for buttons. Maybe we should just not use btn-warning at all. Please take a look at https://bifrost.kolabsystems.com/T315890#2637686 for possible improvement. I'd like to know your opinion.
May 15 2020
May 14 2020
May 13 2020
May 12 2020
Did attached screen help you repeat the error?
May 11 2020
- Log failed payment responses
- Support: Display auto-payment info