Help with bounce emails
Posted
#5926
(In Topic #1229)
My latest experience lead to the following error when configuring the Bounce filter. I properly configured the first page (the mail server settings) and click Proceed. On the next page I received an error message:
"A parameter, TITLE, is referenced in the template, FORM_SCREEN, but not passed"
(see attachment)
Any ideas what may be causing this?
Thanks in advance for your help!
P.S. I tried to add an attachment image of the error message but the "Comcode loading" screen never woiuld stop, and once I clicked on my browser it removed the proposed comcode from this message
Posted
I can't reproduce the "Comcode loading" error you received here. I tried here under your username using Chrome and it attached normally. It could have been caused by some kind of popup blocker or similar, or some random AJAX error. Or a real bug, but I have no way of knowing.
Posted
Thanks Chris. I'm not familiar with Git, can you guide me to where to find these fixes as they are corrected/posted?Chris Graham said
I've just fixed that error message about missing TITLE parameter, but you can ignore it as it won't change the functionality.
I'll try adding a test attachment right now and see if I get the same result as last time…Chris Graham said
I can't reproduce the "Comcode loading" error you received here. I tried here under your username using Chrome and it attached normally. It could have been caused by some kind of popup blocker or similar, or some random AJAX error. Or a real bug, but I have no way of knowing.
From “Post #6621”, 6th Jan 2021
test attachment.txt
Edit #1: nope, tried to do an attachment on my latest post "poll with picture" and I got the same issue – "Comcode loading" forever. Attachments worked with a small text file as noted above, but when attempting with a picture attachmnet it seems to hang with Comcode loading. To get around this issue I had to host the image for the "poll with picture" post and insert the Image to get it to work.
Another thing I noticed is that when adding the Comcode post link in the previous paragraph that I'm getting a "Comdode Helper" message that spins indefinitely…but in this case, the comcode is still getting inserted properly…just the message that sticks around forever. I am using the Vivaldi web browser (chrome based), if that makes any difference.
Edit #2: I just tried with the Microsoft Edge browser and I'm getting the same issue, "Comcode Helper" loading that spins indefinitely...except that with Edge the Comcode tag was still added. But with Vivaldi the Comcode tag gets removed if I click outside the "loading" box. Hope this additional information is helpful.
Last edit: by cwdean
Posted
There's a hot-fix here:
0004213: Missing parameter message when looking for bounced newsletters - Composr CMS feature tracker
I'm worried about getting crossed up with different hot-fixes though, as you've found a few issues and had some custom code. They have to be installed in strict date order if touching the same file(s).
It'd probably be better to hand patch the file as the diff shows here, you can see the single character changed:
Fixed MANTIS-4213 (Missing parameter message when looking for bounced newsletters) (90207e9c) · Commits · Composr ecosystem / Composr · GitLab
Posted
1) Is this with quick reply, or are you replying using the full form accessed via the Reply button?
If it's via the Reply button,
- Do you have the WYSIWYG editor still turned on (it's the default)?
- Are you using the 'Attachments' options on the form? i.e. the below
2) Are you using default attachment settings? If not, what are you changing?
3) Are there any errors in the browser's error console?
4) How big is the file?
5) What is the file type/extension?
Posted
Chris Graham said
It's a one-character change.
There's a hot-fix here:
0004213: Missing parameter message when looking for bounced newsletters - Composr CMS feature tracker
I'm worried about getting crossed up with different hot-fixes though, as you've found a few issues and had some custom code. They have to be installed in strict date order if touching the same file(s).
It'd probably be better to hand patch the file as the diff shows here, you can see the single character changed:
Fixed MANTIS-4213 (Missing parameter message when looking for bounced newsletters) (90207e9c) · Commits · Composr ecosystem / Composr · GitLab
From “Перевод”, 13th Jan 2021
Thanks Chris. I appreciate the concern with me having applied so many hot-fixes. This approach was easy and less risky. Worked great.
Posted
Chris Graham said
Regarding your attachment issue…
1) Is this with quick reply, or are you replying using the full form accessed via the Reply button?
I'm trying to remember
Chris Graham said
If it's via the Reply button,testing.txt
- Do you have the WYSIWYG editor still turned on (it's the default)?
- Are you using the 'Attachments' options on the form? i.e. the below
I don't recall changing anything, but I don't believe the Quote reply has the WYSIWYG editor. I used the New attachment field below the Quick reply box.
Chris Graham said
2) Are you using default attachment settings? If not, what are you changing?
Yes, I don't believe I changed any of the default settings.
Chris Graham said
3) Are there any errors in the browser's error console?
I'm afraid I didn't check, but will do so next time this should happen.
Chris Graham said
4) How big is the file?
5) What is the file type/extension?
From “Post #6641”, 13th Jan 2021
The test text file that I used, that worked, was only a 1k .TXT file. The real screen capture that I wanted to attach was a .JPG file about 200k in size.
Posted
Posted
Chris Graham said
Right. Sounds like some kind of strange JS error, so definitely seeing what is in the console should help. Sometimes these can be caused by things like browser extensions, but I do note you had the problem in two different browsers.
From “Post #6654”, 15th Jan 2021
I did try in both Vivaldi (a chrome-based browser) and Microsoft Edge. The loading issue occurred in both browser. I have extensions installed in Vivaldi, but not in Edge (as I don't use that browser very often). I will definitely look at the browser error console next time.
4 guests and 0 members have recently viewed this.
