jshare
Forum Replies Created
-
Forum: Plugins
In reply to: [a3 Lazy Load] Incompatible with HTTP/2?I know. I have to find another lazy load option. I’m using ngx_pagespeed but I find its lazy load doesn’t work well either.
Here’s the full list right now active:
410 for WordPress
All In One SEO Pack
Antispam Bee
Aweber Subscriber Count
Better Analytics
Better Notifications for WordPress
Broken Link Checker
CSS Cache Buster
Decon Character Counter
Easy Content Templates
Enable Media Replace
Evergreen Post Tweeter
EWWW Image Optimizer
Front-end Editor
Get Custom Field Values
Google XML Sitemap for Videos
Hide Admin Bar From Non-admins
Image Override
Instant Featured Image
JobMobv2 Shortcodes
LeadPages connector
MyThemeShop Theme/Plugin Updater
nginx Compatibility (PHP5)
Paid Memberships Pro
Paid Memberships Pro – AWeber Add On
Paid Memberships Pro – Email Templates Add On
Paid Memberships Pro – Nav Menus Add On
Pretty Link Pro
Q2W3 Fixed Widget
Quick Drafts Access
Social Count Plus
Social Warfare
Theme My Login
Widget Logic
WP Scheduled Posts
WP Sitemap Page
WP-DBManager
WP-Mail-SMTP
WP-Polls
XML Sitemap & Google News feedsWith TML disabled, PMPro is bypassed and all signups are now via the classic WordPress registration. In that situation, 1.3.5 doesn’t generate the User Registration – For User notification, for me at least.
I didn’t think to check the error_log in my test environment before I deleted it, sorry
Forum: Plugins
In reply to: [AMP] Tracking without javascript?How to use Google Analytics to track amp pages:
Forum: Plugins
In reply to: [a3 Lazy Load] Incompatible with HTTP/2?On Firefox, use this addon to show a blue lightning bolt indicator for sites that are fully HTTP/2, like this forum or Google:
https://addons.mozilla.org/en-US/firefox/addon/spdy-indicator/
On Chrome:
Forum: Plugins
In reply to: [Theme My Login] no longer support paidmembership PRO?After digging around, I discovered some things worth mentioning:
Registration is disabled at the network level (I’m on multisite). You can check this by seeing registration is disabled at https://[yoursite]/wp-signup.php
It hasn’t mattered until now, but if I upgrade to 6.4.1, PMPro is now ignored by TML for registration purposes i.e. 6.4.1 exposes the network setting. I can register users again if I enable the setting at the network level in:
https://yoursite/wp-admin/network/settings.php
PMPro is enabled all throughout, but anyone trying to register wouldn’t know it. Only if I rollback to 6.4b2 will new users register again via PMPro.
So yes, 6.4.1 isn’t compatible with PMPro 1.8.6.2 in my view.
I’m also using Theme My Login 6.4b2 if that helps.
Just finished testing in a dev environment.
I’m using 4.3.1 (multisite enabled), PMPro (latest 1.8.6.2). Using 1.3.3, User Registration – For User is generated. Using 1.3.5., it isn’t.
I just tried disabling PMPro, and then I had to enable user registrations for the multisite network in mydomain.com/wp-admin/network/settings.php
However, by doing that, the site now uses classic WordPress registration and a new user receives the Activate and subsequent Login information emails, but not User Registration – For User.
Rolling back to 1.3.3 and using PMPro.
Forum: Plugins
In reply to: [Theme My Login] no longer support paidmembership PRO?Confirmed.
With the latest PMPro (1.8.6.2), everything’s fine on 6.4-beta2. But when I try upgrading to 6.4.1, registration is automatically disabled. Rolling back to the beta immediately restores it.
@ahikmahin you can get older versions from the Developers tab on the plugin page
Forum: Plugins
In reply to: [Public Post Preview] Not working in 4.3It’s now working in 2.4.1
Yes, I’m on 4.3.1
Forum: Plugins
In reply to: [Front-end Editor for WordPress] Compatible with WordPress 4.3?Thanks to that thread, I got this working by changing line 56 in wp-front-end-editor/package.json to 4.4
Forum: Plugins
In reply to: [Simply Pinterest] Pinning is broken when javascript loads synchronouslyForum: Plugins
In reply to: [Super Static Cache] Rewrites on nginx always 403 ForbiddenI think that the problem is for redirects, not rewrites.
I realized that in Direct Mode, a directory was being created for each of the redirects (for example here: /sitemap/). And even though I purged All the cache when switching to Rewrite Mode, that directory wasn’t purged, leading to the error since the server had no index permissions for it.
Once I deleted the directory, the redirect now works.
So the problem is ultimately that when you switch modes, the cache isn’t purged properly.
Forum: Plugins
In reply to: [Social Count Plus] Google : Followers are not countedI initially tried a G+ API Key from a pre-existing project, but the result was a big 0. Only when I tried a new project did this finally work.
Thanks to both of you!