Community @ The Turning Gate

Hey there, Rod.

I assumed it would be in .../backlight/client-response/manage_language/ but I don't see any option to edit these form titles. Anyone know why they aren't in there?

And sure enough, I see what seems to be relevant options in the MAIN language settings: These options appear under the headings "Contact Forms" and "Clients" but even if I change both options to "Your name" etc, nothing changes in any republished (or new) Client Response Galleries. I don't think these options apply to CRG.

I'm getting the same problem in a few areas, in that people don't read things they don't think apply.

I'm amazed how many people get stumped on "where is the submit button?" simply because it's not clearly labelled (and yes, each CRG states "Click on the heart-counter button (top right of this page) to submit your image choices" but apparently very few people read that sentence).

For example, right under the SUBMIT FEEDBACK title on CRG submisssion forms, it clearly states "Please enter your details below" but the font is really small, and people aren't reading it.

They're assuming the form is asking "Where do you want this submission sent to?" when they see the "Name/Email/Message" headings.

This happens so often, it hurts; about 50% of my clients make this mistake, and over 80% of my clients "can't find the submit button".

The only thing I can think to do is to make the UI a little easier to understand for them, but that's proving to be harder than I expected.

Ooooh, I ran into this problem today as well.

Glad to see it was resolved by downloading TTG-Publisher.lrplugin version 4.0.6

Ben- I think it was your awesome suggestion to use a service like Wachete to get notifications of new BL2 modules, but at any instance of /backlight/admin/list_modules/ one has to kind of "guess" if the plugin itself needs to be updated.

Any suggestion on how to know when to update the TTG-Publisher.lrplugin itself?

Is it safe to assume that whenever the other modules need updating, then so does the TTG-Publisher.lrplugin?

I am SO looking forward to it! Thanks again, Matt.

Sorry, I just saw your note. Seems like you noticed this heads-up already!

Any idea about helping to keep mail sent this way out of spam folders?

Edit: It's not a problem when using "send test email" but it does occur when "submitting feedback" a la CRG.

Just to try and limit web hosting variables- I tried using gmail settings in BL2, as per the "more information" bubbles found in the Email Configuration section at /backlight/admin/list_settings/ so it looks like this:

As dead-simple as that looks, I still get "Something went wrong" errors when trying to submit image choices at https://kennethbenjaminreed.com/proofing/example-101/ or when trying to send a test email from /backlight/admin/send_test_email/ (this time with more error info- "fsockopen(): unable to connect to ssl://smtp.gmail.com:465 (Connection timed out) in SMTP.php on line 125").

Update, Rod: That error message now reads

Be careful with this message
This may be a spoofed message. The message claims to have been sent from your account, but Kenneth Benjamin Reed Mail couldn’t verify the actual source. Avoid clicking links or replying with sensitive information, unless you are sure you actually sent this message. (No need to reset your password, the real sender does not actually have access to your account!)

After setting the BL2 email configuration up for SMTP, then reverting it back to "mail", I do now see in the email headers that the emails are no longer coming from box414... they are now coming from ben@kennethbenjaminreed.com.

However, the warning message persists (even though it's slightly different than before), and ultimately I'm trying to "legitimize" the BL2 CRG feedback emails for my clients (these error messages are scary to some people even though I reassure them that everything is working well/safely).

Update: when I send test email from BL2, I get the following error:

Something went wrong

fputs(): SSL: Broken pipe in SMTP.php on line 508:

    fputs($this->smtp_conn, $hello . " " . $host . $this->CRLF);

Thanks, Ben. That sounds likely.

I'm still using the vanilla "mail" setting in BL2.

I now see that Gsuite has flagged the test emails as spam, which only started happening since making the PHP upgrade. Google is warning "Be careful with this message; we could not verify that it actually came from kennethbenjaminreed.com. Avoid clicking links, downloading attachments, or replying with personal information."

So- initial problem solved (the feedback responses are getting flagged as spam) but this now lends me to ask "is there a better BL2 mail setting to use so that clients don't think they are being targeted for phishing attacks, etc by submitting their CRG feedback".

Vanilla mail setting is submitting feedback through box414.bluehost.com rather than my business email address, which is why I assume they are being flagged as potentially dangerous?

Thanks for the suggestion, Daniel.

I've created a few wachete.com "watchets" to notify me of changelog updates.

Looks promising!

Daniel mentioned that as well, and although I am already subscribed... it wouldn't matter, since not all updates are posted. So presently the only course of action we can take is to just keep checking in.

Maybe an option to "receive all update notifications" could be offered in /backlight/admin/list_modules/ so that those of us who care about such things could opt in and those who don't care could opt out?

My first feature request! Sweet!