RafaelLVX
Forum Replies Created
-
Forum: Reviews
In reply to: [All-in-One WP Migration and Backup] Works when it worksThank you for your reply Yani. Those suggestions were already tried earlier, they were not the issue. Looking at the console, I had at some point very early during the upload (like 10-15%) a connection error thrown, which I didn’t capture to be able to post here, but it was one of those typical of when you have an adblocker on, ending with
net::ERR_BLOCKED_BY_CLIENTor maybenet::ERR_FAILED. Getting browser extensions off didn’t help, so I ended up empty-handed. I tend to be willing to isolate and investigate the source of issues such as these and collaborate with devs to help prevent errors in the future, but in this case I was tight on time, so I just moved on with another solution. It wouldn’t have happened if I could just FTP and use the large file like that.Forum: Themes and Templates
In reply to: [Oblique] Update to WP 5.5 breaks the “recent posts” home page.@rakaloah is a life-saver.
If, like me, you’re running a child theme of Oblique, in order to avoid editing Oblique’s own js/vendor/masonry-init.js file (and risking them breaking anything else when they eventually update), you’ll have to do the following:
1. Make a copy of
wp-content/themes/oblique/js/vendor/masonry-init.jstowp-content/themes/oblique-child/js/vendor/masonry-init.js(or whatever your child folder is at).
2. Editwp-content/themes/oblique-child/js/vendor/masonry-init.js, change line:
var colGroup = this._getColGroup( colSpan );
to:
var colGroup = this._getTopColGroup( colSpan );
3. For that to stick, you need to kill their script late and enqueue your own as per this answer. To do that, simply add this function at the end of yourwp-content/themes/oblique-child/functions.phpfile:// Fix broken outdated Oblique masonry script. add_action('wp_enqueue_scripts', 'child_masonry_fix', 100); function child_masonry_fix() { wp_dequeue_script('oblique-masonry-init'); wp_enqueue_script('child_oblique-masonry-init', get_stylesheet_directory_uri().'/js/vendor/masonry-init.js', array( 'jquery', 'masonry' ), true ); }Note that your functions.php might already have other wp_enqueue_scripts in there, but in my experience you should enqueue this separately so it gets loaded late (I believe that’s what the “100” property does).
Hope this helps!
On my end, redirecting to wp-login.php without the / is what works. When we’re trying to access protected pages logged off, it redirects to domain.xxx/wp-login.php.
I only wanted to block access to a specific category of articles, and I wanted everyone logged in to get access, so I set up only one access level, “logged in”. Because of the issue, I tried with specific roles like Administrator, happens the same. I stuck to logged in.
My plugin list has a few possible culprits, but they never gave me issues before:
– Attachment Pages Redirect
– Breeze (caching, and I also use Varnish)
– Cloudflare
– Redirection by John GodleyI have a Knowledge Base for Documentation & FAQs plugin by Echo Plugins. That creates articles with a specific category (usually “Docs”, in my site I called them “Como Faz”). That is the part of the site I wanted to restrict access to, so if you go to https://miniagencia.com.br/comofaz or https://miniagencia.com.br/comofaz/configurando-emails-no-hostgator it’ll instead redirect you to the login page. I did that by creating an access level for the Como Faz page and Como Faz articles, where Members are Synchronized Role Logged-in, action is Redirect->wp-login.php, all the rest I left as default.
I’m no expert, the reason I think this has to do with cache is because I read that when a site A redirects 301 to site B, Firefox will take that to heart and will never again access site A, instead going straight to site B if you try to access site A. Also, when I clear cache on Firefox, I can login beforehand and it works as expected, with no fuzzy redirection. The problem with this sort of caching is that you can’t clear it by refreshing of Ctrl F5, because it skips the original site address you want to access. You have to manually go into the cache panel of your browser, and find the site there, that’s a hassle.
Now I’ll test deactivating those four plugins, see what happens.
Huh, you see, deactivating those plugins fixed the issue, and then reactivating them didn’t bring the issue back. I wonder what that means. Will them break my access again later when they rebuild whatever broken functionality they tried to serve?
I could confirm I see this issue using Chrome too. I usually only use Firefox. I don’t see this issue while using Edge.
Anyway, it’s fixed on my end now, I can’t say much more.
I think you need to put “wp-login.php” without a “/”.
I think you need to put “wp-login.php” without a “/”.
Forum: Plugins
In reply to: [Easy Social Share Buttons] Sharing from blog index shares arbitrary blogpostAnd I found my own solution:
Advanced Settings > Advanced Options > Plugin does not share correct data > Correct share data when sidebar, top bar… > YES
That did the trick here.