Title: jeffmart's Replies | WordPress.org

---

# jeffmart

  [  ](https://wordpress.org/support/users/jeffmart/)

 *   [Profile](https://wordpress.org/support/users/jeffmart/)
 *   [Topics Started](https://wordpress.org/support/users/jeffmart/topics/)
 *   [Replies Created](https://wordpress.org/support/users/jeffmart/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/jeffmart/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/jeffmart/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/jeffmart/engagements/)
 *   [Favorites](https://wordpress.org/support/users/jeffmart/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)

1 [2](https://wordpress.org/support/users/jeffmart/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/jeffmart/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] REACTJS issue after upgrade](https://wordpress.org/support/topic/reactjs-issue-after-upgrade/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [1 year ago](https://wordpress.org/support/topic/reactjs-issue-after-upgrade/#post-18442316)
 * Thank you for your attention, Maybellyne,
 * Unfortunately, our site operates in a high availability segment, and we currently
   do not have a parallel development environment, so none of the options are viable
   for me. The Health Check & Troubleshooting plugin, which you mentioned, has received
   many complaints about causing problems to sites, so I cannot risk taking our 
   site offline.
 * In any case, considering that during this entire period we have not changed any
   plugins and the problem started precisely when we updated Yoast and WordPress
   in the same week, even if it is another plugin causing this, we will have to 
   find an alternative, since we would have difficulty deactivating any of the (
   few) other plugins, since they operate on features delivered directly to visitors,
   on the frontend.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] REACTJS issue after upgrade](https://wordpress.org/support/topic/reactjs-issue-after-upgrade/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/reactjs-issue-after-upgrade/#post-18434046)
 * Hi [@maybellyne](https://wordpress.org/support/users/maybellyne/),
 * Clearing the caches (yes, we have multiple caching strategies in place), then
   disabling them completely, logging into the backend from an incognito browser
   window, and then doing the same process in a completely new instance of another
   browser that was just installed specifically for this task were the first tests
   we did before I came here to report the issue. So, well, I’m pretty sure it’s
   not a cache-related issue…
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[LiteSpeed Cache] Error connecting to Quic.cloud after upgrade from 6.5.4 to 7.X](https://wordpress.org/support/topic/error-connecting-to-quic-cloud-after-upgrade-from-6-5-4-to-7-x/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/error-connecting-to-quic-cloud-after-upgrade-from-6-5-4-to-7-x/#post-18394542)
 * Well… I’m not sure the proposed solution of whitelisting the IPs makes much sense
   in my case.
 * After checking the server and firewall security settings, I noticed there are
   no blocked IPs and ports 80/443 are open to any IP.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[LiteSpeed Cache] Error connecting to Quic.cloud after upgrade from 6.5.4 to 7.X](https://wordpress.org/support/topic/error-connecting-to-quic-cloud-after-upgrade-from-6-5-4-to-7-x/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/error-connecting-to-quic-cloud-after-upgrade-from-6-5-4-to-7-x/#post-18394514)
 * Ah, I see… These IPs need to be allowed on our server… But please explain… Considering
   that the only change was the update, why is it necessary to check this now, and
   before it wasn’t?
 * Another question. There are many IPs… I don’t think it’s a good policy to allow
   any port… Can I restrict the release to ports 80 and 443?
 * Thanks,
   Jeff
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[LiteSpeed Cache] Error connecting to Quic.cloud after upgrade from 6.5.4 to 7.X](https://wordpress.org/support/topic/error-connecting-to-quic-cloud-after-upgrade-from-6-5-4-to-7-x/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/error-connecting-to-quic-cloud-after-upgrade-from-6-5-4-to-7-x/#post-18394428)
 * No, our IP is not on this list. Should it be? I don’t think this is a change 
   that happened between versions 6.5.4 and 7.0.0. At least not because of changes
   on our side…
 * Jeff
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[LiteSpeed Cache] Failed to communicate with QUIC.cloud server: Unknown error: unknown [server]](https://wordpress.org/support/topic/failed-to-communicate-with-quic-cloud-server-unknown-error-unknown-server/)
 *  [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/failed-to-communicate-with-quic-cloud-server-unknown-error-unknown-server/#post-18388698)
 * Same here, running openlitespeed server 🙁 Communication is normal with 6.5.4
   version, but errors in 7.0.0 and 7.0.0.1
 * Jeff
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[ColorMag] “Read more button” translation](https://wordpress.org/support/topic/read-more-button-translation-4/)
 *  [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/read-more-button-translation-4/page/2/#post-17545826)
 * This worked for me in custom CSS:
 *     ```wp-block-code
       .cm-entry-button span {
       display:none;
       }
   
       .cm-entry-button {
       display:visible;
       }
   
       .cm-entry-button::after {
         content: " Text here";
         color: #ffffff; /* color adjust if needed */
         padding: 4px 12px; /* padding adjust if needed */
         visibility: visible;
       }
       ```
   
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Too many issues with last update](https://wordpress.org/support/topic/too-many-issues-with-last-update/)
 *  [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/too-many-issues-with-last-update/#post-13239942)
 * Ok… Apparently all the errors solved using the “Enable jQuery Migrate Helper”
   plugin (many, many even … in various functions, native or plugins). So, it´s 
   clearly a jQuery Migrate Helper related issue…
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Too many issues with last update](https://wordpress.org/support/topic/too-many-issues-with-last-update/)
 *  [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/too-many-issues-with-last-update/#post-13239908)
 * Same problem here… Well, by the way, multiple problems … Inserting media does
   not work … When using the classic editor plugin the “text mode” tab does not 
   work … When trying to edit with block editor it gives an error message (something
   related to the Yoast plugin) , if you disable the classic editor plugin it will
   continue to open in “classic editor plugin” mode! The code “define (‘CONCATENATE_SCRIPTS’,
   false);” does not solve anything … Of course the problem is related to plugins
   and their compatibility … but does anyone use WordPress without any plugins?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] 5.5 Classic Editor Text View / Add Media Not Working](https://wordpress.org/support/topic/5-5-classic-editor-text-view-add-media-not-working/)
 *  [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/5-5-classic-editor-text-view-add-media-not-working/#post-13239881)
 * Same here! And I can’t use block editor too… If I try, get an error message…
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[SuperMag] Responsive ajust problem](https://wordpress.org/support/topic/responsive-ajust-problem/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/responsive-ajust-problem/#post-12097284)
 * Dear [@acmethemes](https://wordpress.org/support/users/acmethemes/)
 * This customization is already part of the interim solution of the problem. Just
   after the problem, I added this code in the media query, so things are all inside
   the viewport. Otherwise the white ribbon is left on the off-screen side, and 
   Google Search Console points out three errors in “Mobile Features”: content larger
   than the screen, clickable elements too close and text too small to read … I 
   just was able to validate corrections after this workaround, which is far from
   a definitive solution…
 * If I go back to the original query, the problem reappears. And no, I didn’t have
   this problem before the last update.
 * Best regards!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[OneSignal - Web Push Notifications] Version 1.17.7 BROKE SCHEDULED POSTS AGAIN…](https://wordpress.org/support/topic/version-1-17-7-broke-scheduled-posts-again/)
 *  [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/version-1-17-7-broke-scheduled-posts-again/#post-11780030)
 * The latest version of the plugin has another problem with scheduled posts. The
   Push, except for me, is correctly sent, but using the URL with the Post number(/?
   p=xxxxxxx), not the post slug. It causes problems tracking, indexing and when
   we use additional parameters in the URL that repeat the sign “?” to add Google
   Analytics tags or any other code.
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[ColorMag] The visibility widget resource is not working](https://wordpress.org/support/topic/the-visibility-widget-resource-is-not-working/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/the-visibility-widget-resource-is-not-working/#post-11686828)
 * I’m trying to use one of the “Featured Post” widgets. Specifically the “TG: Featured
   Posts (Style 1)”.
 * As in the link image:
    [https://themegrill.com/wp-content/uploads/2015/04/colormag-instruction-vertical-post-widget.png](https://themegrill.com/wp-content/uploads/2015/04/colormag-instruction-vertical-post-widget.png)
 * Initially I determined the use of a category, with the exclusion / disregard (
   via “Visibility”) if it was in any of the other two categories, selected with“
   Hide if” -> categories (open condition for any, not restricted to all conditions).
   Does not work.
 * Both, using separate categories and using exclusion categories as the “child”
   of the main category, it still shows all posts, even creating the filter to not
   display if it also belongs to the other categories.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Auto Post WP to Photo Social Network] Request new features and comments on bugs](https://wordpress.org/support/topic/request-new-features-and-comments-on-bugs/)
 *  Thread Starter [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/request-new-features-and-comments-on-bugs/#post-11645904)
 * Hi dufour_l!
 * It is a great news! Great job!
 * Thank you very much!
 * Regards!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Yoast SEO box problem in new posts](https://wordpress.org/support/topic/yoast-seo-box-problem-in-new-posts/)
 *  [jeffmart](https://wordpress.org/support/users/jeffmart/)
 * (@jeffmart)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/yoast-seo-box-problem-in-new-posts/#post-11314936)
 * I think that problem isn´t exactly in OneSignal and Yoast… For me, issue just
   appears if I use classic editor. In Guttenberg, Yoast and OneSignal are working
   fine…

Viewing 15 replies - 1 through 15 (of 20 total)

1 [2](https://wordpress.org/support/users/jeffmart/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/jeffmart/replies/page/2/?output_format=md)