• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Problem with PUP/SMF

Status
Not open for further replies.

Jailer

Chevereto Member
Was something changed with the PUP in the latest update? I can't seem to get it to work via the embedded button in the editor toolbar. It doesn't work for PM's or for posted messages. The pop up window opens and the pics are uploading to my Chevereto site but they aren't posting the image bbcode in the message body when you hit the upload button. The large button below the quick reply box is still working as expected though.

I've checked the server logs for the forum and for my pics hosting site and there's no indication of any error. My forum log shows no errors either. Console message in Chrome doesn't show any errors when trying to upload either. I'm kinda stumped at this point and it's making troubleshooting a bit difficult.

Any ideas?
 
Don't know if this makes a difference or not but I'm getting different output in the console in firefox depending on where I try to upload a pic from. Again the only button that is working is the quick reply button.

The console messages:


from quick reply box

Code:
<textarea cols="600" rows="7" name="message" tabindex="1" data-chevereto-pup-target="20ea4dc9-bddf-47a1-85aa-f758b83ce1c1">


from reply box

Code:
<textarea id="message" class="editor" name="message" rows="12" cols="600" onselect="storeCaret(this);" onclick="storeCaret(this);" onkeyup="storeCaret(this);" onchange="storeCaret(this);" tabindex="2" style="height: 175px; display: none;" data-chevereto-pup="sibling" data-chevereto-pup-target="e183494e-5f60-4d4e-b592-2f3035e451f3">


from PM message box

Code:
<textarea id="message" class="editor" name="message" rows="12" cols="600" onselect="storeCaret(this);" onclick="storeCaret(this);" onkeyup="storeCaret(this);" onchange="storeCaret(this);" tabindex="4" style="height: 175px; display: none;" data-chevereto-pup-target="f9568acc-6718-40ee-b2d2-78d12aadfd48">
 
The console won't tell you anything as PUP runs in its own closure. I have to check it on my own.
 
Well hells bells. I'm lost and don't even know where to begin to troubleshoot this. I get no errors reported anywhere. 🙁

If anyone has any suggestions I'm all ears.
 
Last edited:
Yes. It was brought to my attention by one of my board members that was also having issues with it and it doesn't seem to be working for anyone. I did ask over on the SMF fourms and other users are not having any issues so it's definitely a problem on my end. It's going to take me a bit to figure out though since nothing was changed in the configuration of either server so I don't even know where to start.
 
Both sites are https and have been since their creation. Was working fine until just recently and I've done nothing but update to the latest version of Chevereto and update the packages for both (FreeBSD). I have literally changed nothing in the configuration.
 
Well, send me a PM with your Chevereto URL so I can check that. I tried to access to the forum but I got a connection timed out.
 
Does anyone have any ideas on how I would go about tracking this issue down? I've even set the server log level to debug and there is NOTHING in the log indicating there is a problem. I just can't figure out why this is working when using the quick reply button but not when using the button on the editor.

I literally spent all day trying to figure this out and I'm out of ideas. 🙁
 
Pup doesn't work on the server layer so the server won't have any log of it. Pup does everything on the client layer.

Pup uses postMessage API to handle the message from your Chevereto installation to the target editable content (textarea or whatever). If the button is being shown and the picture gets uploaded, then the problem is in the postMessage API which could be limited by your website/browser settings.

There's is a "pup.dev.js" file that you could use to debug.
 
Thank you for your reply Rodolfo. You're reply actually got me thinking about the textarea and what could be different and I finally figured it out. I had the WYSIWYG editor enabled in my forum profile and that is the problem. With the WYSIWYG editor disabled the URL is pasted correctly as it should be. With it enabled it doesn't work. There is no WYSIWYG option available on the quick reply so that's why it was working there.

Now to see if SMF is actually receptive to fixing the problem on their end, the devs can be a bit picky about their baby.

Thank you for helping me work through this.
 
Ah... the infamous SMF WYSIWYG editor 😱

The WYSIWYG editor in SMF 2.0.x is very buggy and has had all sorts of problems for years. No one should be using it really, let alone with Chevereto. It's been replaced in 2.1 but that's still in Beta.

With 2.1 in the wings I can tell it won't be fixed in SMF. In 2.1 it's built into the core but it can not be backported into 2.0.x

You could try an alternative editor like the SMFPacks one: https://www.smfpacks.com/wysiwyg/ No idea if it's any good as I haven't tried it myself.
 
Last edited:
Eh, my guys are pretty simple so I'm just going to disable it. They can get by without a fancy editor and most likely won't even notice it.
 
Status
Not open for further replies.
Back
Top