Closed creecros closed 1 year ago
@alfredbuehler This is due to an infinite loop created by the Folders feature.
$this->template->hook->attach('template:config:email', 'mailmagik:config/config', array(
'folders' => $this->helper->mailHelper->getFolders(),
));
The plugin dies here in Plugin.php and therefore will never load when it cannot authenticate.
Fixed by b63be9bfc5aab0d97cc51c1280ea35847b583ae6.
not quite. now it dies in the config when it hits the INBOX.
its been wrapping my brain....
For testing, I have removed my password from the settings. So I'm unable to login and get the folder list. But I don't see any errors.
i dont have any errors either, i am guessing there is a die()
somewhere in the vendor library. im currently clueless, and have been looking at it for an hour already.
But how did you get the screenshot above?
when i say i have no erros i mean, in my logs. but it clearly dies when loading the config, and it dies at the Folders, since that is where the code stops.
What says the Webservers log?
my nginx log is empty....
I tried to enforce with the wrong credentials, no way. Furthermore, not with another IMAP server. Everything works here.
whats your KB version and php? I'll try to match and see if its related to my version somehow
I'am not deeply in that topic, but maybe it is possible to do a test upfront if a connection is possible and then if not force the user to remove the imap config / clear it or to correct it?
Only in case of a working connection the plugin goes on?
Just asking. Sorry if this is nonsense.
Maybe this helps
This is the environment where i can reproduce this issue
So you can reproduce it? Then its not a version thing.
Curious that alfred cannot reproduce.
I'm in a meeting for another 30 mins, then ill pick this back up.
Moment! Not for actual changes!
I may test this if i get the latest code
Just let me know if i can assist - short explanation how 😄
I'm getting closer, so let me fix it.
Do your thing! ;-)
sounds good, i wont parallel you this time i swear!
What about a discord place for such things?
you are always welcome to chat me, creecros#4914
Silly question? How does that work?
I'am thinking about a chat chanel in general, but for such issues an other chanel is more than sufficent
you just make a channel and start inviting people. like this.
I know 😄
But i'am unsure if this is something people like to use and i would preferre to allow "others" as well to use...
I can start such a chanel.... but how can i tell... i would like to have support to do so....
I am so confused by the question. maybe it is the language barrier.
the only way to know, is to try I guess. I would say, more people are likely to use discord since they are computer oriented people, who more than likely have played a video game in their life, than use something like slack, which is to far to the left for me.... :smile:
I think you understood 😄
Maybe i start a channel...
Off for now.
I wish you a nice, relaxing weekend!
Meanwhile, I know the source, but not the solution.
That crappy "new Mailbox" doesn't throw an InvalidParameterException nor does it return false, both as documented, when we pass bogus arguments to the call. How can we check the validity of a mailbox then? I'm still on it.
I solved it, can i push?
i pushed.
might make more sense to move that logic up into the login() function so that the function will return false, but basically we need to login, and then test the connection to determine a false.
sounds good, i wont parallel you this time i swear!
Thank you for the fish! :(
How can we check the validity of a mailbox then?
it sounded like you were asking me, and so i found the answer, figured you would notice the push. my bad.
From #25 by @JustFxDev
0.) Fatal Error An incorrect imap e-mal password or something like that disables the plug in. It disappears from the list of installed plugins. This leads to this situation: I cannot correct the password in the application setting / e-mal setup. The fields are no longer there.
Even a new installation does not change this, because the wrong information is still in the database.
I fixed that by changing it directly in the database.
That occurred also as the server had certification problems (this was the reason why I found that initial out)
Error-log: [xx-xxx-xxxxx xx:xx:xx Europe/Berlin] [critical] Mailmagik: ["Can not authenticate to IMAP server: [AUTHENTICATIONFAILED] Authentication failed."]