Re: DB oversizing images issue
You closed the second thread about the topic without be solved again: https://support.brizy.io/hc/en-us/requests/6543
A ticket should be closed just when the error is solved or an ETA is given. I can not keep that super admin password for the developer for something that is a global error. I did not even get why he asked me that, since the error happens with every single installation and can be easily reproduced and seen.
Did he see the error and I can change my password now? What is the ETA for that? I am about one year waiting to be really able to use Brizy, since with that issue, very soon I would have database issues.
Thank you!
-
Hi Diego,
First of all, we do not close the tickets on zendesk. This is done automatically by the system after a long period of inactivity.
The problem reported by you has already been fixed and will be included in the next update. A new update has been planned for today, but we will release one after the weekend. So you can change the password.
Sorry for not having more communication with you and thank you for your patience.
0 -
Hi, I suggest u guys to change the Zend config then, that can mess up things for everybody.
Weird, I am not seeing this ticket on my requests (https://support.brizy.io/hc/en-us/requests), just by e-mail.
I did not see that in the changelog, is there a reason it was not inserted there or were you mistaken about the update fixing the DB oversize issue? Thank you!
0 -
Brizy project keeps showing up on DB. What exactly is that? Seems to be a token relating to Brizy Cloud, which I do not use. There is this information there after the token: brizy-cloud-token";N;s:19:"brizy-cloud-project
Do you know what is the problem I was talking about to Natalia? Are you the coder? Thank you.
0 -
Hi,
This is not a ticket. This is a post on our forum/community and you can see it here in your account: https://jmp.sh/Jj9DjFn
Not, I'm not a coder. Also, I just had a word with our devs and that fix was not introduced in the latest update. Sorry about that. It seems that more tests are needed and it was not ready for this update even though it was already fixed.
Regarding the brizy-cloud-token: I don't think this is related to the issue discussed with Natalia. I will check this with devs.
0
Please sign in to leave a comment.
Comments
4 comments