vitruvian1man

Good news.

I got to thinking that I might need to actually publish a new post to really test whether the campaign email is being scheduled and sent, so I finally got around to publishing a blog post last night.

I didn’t see any email notification about it in my mail last night or this morning, so I looked at Icegrams report, and it did show a new campaign email scheduled to be sent. So, I clicked send, and seconds later the email was received in my inbox.

So it works.

Regarding the test emails not being received from my initial inquiry posted here and to which you responded, it turns out there was a long delay in actually receiving them. After I had sent the test emails, I continually checked my email (including bulk/spam) and also clicked ‘get new messages’ in my email client.

Nothing from Icegram appeared even after a couple of hours, so I went to bed. The next morning, I noticed they all were received in my in-box, with the appropriate time stamp of when I sent them (the prior night). So, there was some sort of delay, at least more than 2-3 hours, before they were received. Regardless, they were received.

So, I think it is working.

Thank you for your timely and kind follow-up. I’ll mark this post as resolved, even though I didn’t make any changes.

• This reply was modified 3 months, 2 weeks ago by vitruvian1man.

I got my issue resolved from a WPForms’ person via direct email because I had also sent an inquiry by a form.

I only changed the code snippets provided (see below) to include my own custom colors and the !important statement as such:

{
background-color: #FAF243 !important; /* Yellow background */
}

{
background-color: #e5da00 !important; /* Darker yellow background */
}

Here is the CSS snippets that were provided. As mentioned, they work provided one puts in that statement, !important.

/* Change submit button color / div.wpforms-container .wpforms-form input[type=submit], div.wpforms-container .wpforms-form button[type=submit] { background-color: #FAF243; / Yellow background */
}

/* Change submit button's hover color / div.wpforms-container .wpforms-form input[type=submit]:hover, div.wpforms-container .wpforms-form input[type=submit]:active, div.wpforms-container .wpforms-form button[type=submit]:hover, div.wpforms-container .wpforms-form button[type=submit]:active, div.wpforms-container .wpforms-form .wpforms-page-button:hover, div.wpforms-container .wpforms-form .wpforms-page-button:active { background-color: #e5da00; / Darker yellow background */
}

• This reply was modified 3 months, 2 weeks ago by vitruvian1man.

Update:

As a final update, I deactivated and uninstalled Astra and then installed/activated a different theme. Before doing so, I reviewed six more themes focusing on full site editing (FSE) using the block editor. All of the themes that I tested via live preview worked properly with respect to aligning the blog excerpt below the archive’s featured image regardless of the size of the image.

Switched theme:

I decided to install a theme named Blocksy, which works quite well (here’s the screenshot).

It has a lot of similar customization features as Astra’s theme.

To my surprise, it also included a couple of neat features in the non-premium (free/donations only) version: (1) a sticky sidebar, (2) both “published date” and “modified date” for blog posts, which is helpful for readers to know that an older blog post has been updated, and (3) a lot of customization options for typography, colors, dark mode, etc.

Conclusion:

The issue I experienced with Astra could be something with the install itself on my end since you and others haven’t reported this issue, from my understanding.

I will re-install Astra in the future to give it another test. Until then, it appears I got lucky and found a theme in Blocksy that’s exceeded my expectations.

I appreciate your initial follow-up.

I appreciate your looking into the issue.

Since you’re showing the theme aligns properly on a dev site, I tried more basic troubleshooting on my end.

Plug deactivation:

I de-activated all plugs, cleared cache, and then viewed the blog archive page and Astra’s theme still mis-aligns the excerpt on posts that have smaller-width featured images (screenshot link). Astra places the excerpt to the right of the image and uses a wrap feature.

Test other themes:

So, I tried a couple of random themes to determine whether they also mis-align the excerpt like Astra’s theme does.

First, I tried WordPress’s Twenty Twenty Four theme. It worked properly. The blog archive showed proper alignment of excerpts (below the image) regardless of the featured image size.

Then, I tried another theme, Mirror Magazine, and it also worked properly (screenshot link).

My Conclusion:

Based on my limited tech experience and testing of a couple of other themes, it appears, for some unknown reason, that the blog excerpts mis-align when using the Astra theme on my site/server.

I guess, for now, I’ll just plan to use a different theme since doing so eliminates the problem at my end.

I appreciate the thorough response. A Brainstorm representative finally explained the problem, which you also noted:*

* If the base theme is updated but the Pro Plugin is not updated (i.e., purchase another annual license), then the Pro Plugin will not work (in my case and probably many others) conveniently due to “compatibility issues.”

__

So, I and others may either (A) revert back to an older version of the Astra base theme (opens up potential vulnerabilities) in order return compatibility to the purchased Pro Plugin, or (B) keep the most recent updated version of the base Astra theme and forgo the use of the purchased Pro Plugin since it would be incompatible with an updated version of the base Astra theme.

End result: Customers are essentially compelled to update the Pro Plugin (i.e. purchase another annual license) otherwise they will most likely experience “compatibility issues.”

Of course, if one is handy with code, one could make the necessary changes to the code.

I will elect to use another theme by a different provider — either entirely open-source or from an author with honest and transparent policies regarding “compatibility issues.”

Thank you, @bsfherman. Your CSS code snippet worked. Much obliged for such a prompt response, too.

I also experience the problem OP shared regarding putting 0 px for size of tagline, but the system will revert to a default size and still display the tagline.

I’m trying to hide the tagline on tablets and mobile, and keep the tagline for desktops.

Since you mentioned that a CSS code snippet can solve this problem, I tried various codes but can’t get any to work properly. Will you point me to where I can find the proper CSS code snippet to hide tagline on tablet & mobile?

I’ve tried this snippet, which doesn’t work for me:

@media (max-width: 1000px) {
    p.site-description {
        display:none;
    }
}

Thank you, @abidhasan112 , for the prompt reply/feedback and CSS code snippet. It worked well for me.

Regards,

I looked into the theme, which is using a child theme. In the child theme folder, I reviewed the functions.php file and it had some code in it to defer javascript. So, I removed it and tablePress works perfectly with all the dynamic features.

Anyway, here’s the snippet of code that I removed:

// Defer Parsing of JavaScript in WordPress via functions.php file
// Learn more at https://technumero.com/defer-parsing-of-javascript/ 

function defer_parsing_js($url) {
//Add the files to exclude from defer. Add jquery.js by default
    $exclude_files = array('jquery.js');
//Bypass JS defer for logged in users
    if (!is_user_logged_in()) {
        if (false === strpos($url, '.js')) {
            return $url;
        }

        foreach ($exclude_files as $file) {
            if (strpos($url, $file)) {
                return $url;
            }
        }
    } else {
        return $url;
    }
    return "$url' defer='defer";

}
add_filter('clean_url', 'defer_parsing_js', 11, 1);

Thanks again for your guidance and solution.

Thank you for identifying the problem. I will take some time to figure out where the defer='defer' is being added and then remove it. I’ll mark this support request as resolved, too.

I appreciate such a timely followup. I just deactivated and then deleted jQuery Migrate Helper plugin.

Update as of Fri. 01Jan2020 12:20pm ET USA:

After I deactivated all plugins and cleared cache and then tested tablepress, the same error in the console was generated.

The website’s theme is Astra – pro – child theme and I believe it has had some custom code put into a child functions.php file, not sure whether that could be interfering with tablepress.

Also, this is the other info about the setup that I overlooked providing in my initial inquiry:

· Website: [reference prior link provided to the blog post that is using a table by tablepress]
· TablePress: 1.12
· TablePress (DB): 41
· TablePress table scheme: 3
· Plugin installed: 2020/12/29 19:32:06
· WordPress: 5.6
· Multisite: no
· PHP: 7.4.13
· mysqli Extension: true
· mySQL (Server): 10.3.27-MariaDB-log-cll-lve
· mySQL (Client): 10.3.27
· ZIP support: yes
· UTF-8 conversion: yes
· WP Memory Limit: 40M
· Server Memory Limit: 1M
· WP_DEBUG: false
· WP_POST_REVISIONS: true

Well, I changed a couple of settings and it shows that it is now blocking emails.

I changed the first setting listed in my initial post to automatically use the best method (excluding javascript).

Thank you for such a prompt response, Abid. I’ve subscribed to this conversation so I’ll get updated from you/your team when the dev team is able to fix. Cheers.

Simple solution! It turns out the problem was with the integration with Google’s v3 ReCaptcha. I removed the keys and CF7 can successfully email. So, the PHP upgrade might have caused a problem with the security keys/integration. I’ll probably just need to reinsert the keys.

However, I plan to test CF7’s native functionality — Quizes and/or HoneyPots.

By the way, my other form by SendInBlue uses v2 Captcha, which probably explains why it wasn’t affected by the PHP upgrade.

Yes, your solution worked, (@prismtechstudios.

@media print { 
  .modern-footnotes-footnote { display: none; }
}

Much obliged. My apologies for a delayed response — overlooked the notification regarding your response.