Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter DManIT

    (@dmed)

    Hi @alextonio22,

    Thanks for the reply! Both plugins were updated. I did report this to GravityKit and their response was:

    “Regarding that fatal error with LifterLMS, it’s a code issue on their plugin. Please share this with them (LifterLMS):”

    ..followed by the stack trace I provided in my first message.

    GravityKit stated this is an issue with LifterLMS and it appears the issue in the stack trace is in the lifterlms/includes/class.llms.integrations.php file. Is this incorrect?

    • This reply was modified 2 weeks, 6 days ago by DManIT.

    I can confirm I’m seeing this issue as well, searched for it on Google and found this post. Glad to see it’s a known bug and a fix is in the works.

    I too was looking for the widgets in the TT4 theme and was frustrated to find they were missing while there’s no clear guidance on a replacement. As jordesign suggested, you can manually add blocks anywhere you want, but this does not replace widgets where you can update the content in one place and it will update all instances. This is the real benefit of widgets.

    You can add blocks to the footer or header, but if you don’t want the same blocks on each page this will not work. Also, as far as I can tell, there’s no native way to add conditional logic to a block to determine when and where it might be shown.

    Another option is to use template parts which are in some themes like TT4. This has no conditional logic but provides a reusable part to add to pages.

    If you need conditional widgets/blocks like I do, for varied content in a section on multiple pages/sections that can be updated in one place, I think there may be some option with JetPack or a plugin like conditional blocks.

    Thread Starter DManIT

    (@dmed)

    I’ve switched to using a a PDF viewer but I prefer the LeafLet image option. Any suggestions to reduce the initial zoom level on a larger image file?

    @fiendishlyclever I don’t see the HTML tags on the test emails on any of the SMTP plugins. I only see the HTML tags from the Jetpack contact form when using the Postman. Using the WP SMTP plugin the contact form never delivered the emails. I disabled these and installed Easy WP SMTP which fixed both issues with the Jetpack contact form.

    @lschuyler I tried reverting between Postman and WP SMTP several times and the HTML tags always showed in the contact form email with Postman and the email was never delivered with WP SMTP. Neither plugin provides any formatting options. I can only send via SMTP from my server so I can’t test without a plugin.

    I’m thinking there is a bug or missing tag somewhere in the Jetpack contact form that breaks these plugins.

    I tried another WP SMTP plugin, Easy WP SMTP, and the contact form email no longer shows the HTML tags. Maybe this is an issue with how both Postman and WP SMTP integrate with JetPack contact forms?

    I’m having the same issue and other issues with the Jetpack Contact Form. It seems generally broken.

    Using Postman plugin, contact form sends visible HTML in the email body. Email body looks like this:

    <!doctype html>
    <html xmlns="https://www.w3.org/1999/xhtml">
    <body>
    
    <b>Name:</b> Joe<br /><br /><b>Email:</b> [email protected]<br /><br /><b>Website:</b> <br /><br /><b>Comment:</b> Test<br /><br /><br /><hr />Time: April 12, 2017 at 4:22 am<br />IP Address: xxx.xxx.xxx.xxx<br />Contact Form URL: https://www.mydomainname.com/contact-us/<br /><p>Sent by an unverified visitor to your site.</p>
    
    </body>
    </html>

    I was using the WP SMTP plugin before trying the Postman plugin. With the WP SMTP plugin, I could send test emails from the plugin but the contact form emails were not received via email. They are logged in Feedback but no setting would deliver them to an inbox.

    I like the simplicity of the Jetpack contact form but this is a big issue. Will need to use another plugin if this can’t be fixed.

    • This reply was modified 7 years, 7 months ago by DManIT. Reason: typo
Viewing 7 replies - 1 through 7 (of 7 total)