Micah Wood

@jannepalmen At the moment, no. However, this is a feature that could definitely be added. I’ve added a task for this here: https://github.com/wpscholar-wp-plugins/random-post-on-refresh/issues/12

One consideration here is the date format. I think by default it would make sense to use the format set in the WordPress settings, maybe with an override somehow via the shortcode.

@tkaprol Thanks for alerting me to this. I’ve just released version 1.2.8 which fixes the issue.

@jeppeh That function is a WordPress core function introduced in WordPress 4.7. I think the only way that could break things is if you are running the plugin on a WordPress version less than 4.7. Granted, it looks like I’ve incorrectly labeled the plugin as compatible with WordPress 4.0 or greater, so I’ll get that updated.

Another possibility is that your WordPress installation has been compromised or is missing some files from a botched installation.

Awesome!

@9b01 Yes, when full page caching is enabled the refresh functionality will not work as expected. I’d recommend excluding pages using this shortcode from being cached.

See: https://getwpo.com/documentation/#Advanced-settings-exclude-URLs

My plugin would redirect all the URLs on the site to the same URLs on the new site. The recommendation would be to have the appropriate redirects set up via RankMath on the new site should any of your content be changing URL paths.

For example, let’s say you’re currently redirecting a page from /original/page/ to /new/page/ on the old site and now you want to point olddomain.com/original/page/ to newdomain.com/new/page/. The Simple Website Redirect plugin would handle the redirect from olddomain.com/original/page to newdomain.com/original/page. RankMath on the new site could handle redirecting from newdomain.com/original/page to newdomain.com/new/page.

If moving the redirects in RankMath from the old site to the new site isn’t feasible for you, then I wouldn’t recommend using my plugin as it could potentially conflict with your existing redirects.

If you have an Apache server, you can also try redirecting just the homepage like this: https://stackoverflow.com/questions/31281346/redirect-website-homepage-only

• This reply was modified 3 years, 8 months ago by Micah Wood.

This plugin only handles a single redirect of the entire site. It sounds like you may have it confused with another redirection plugin? There is only one redirect and it should be remembered.

Awesome! Thanks for letting me know!

@salmanjaveed Version 1.1.3 should fix this issue for you. Turns out the issue only happened when the Yoast SEO plugin was active, but the issue was in my code.

Thanks!

The Blank Slate plugin doesn’t really have any say in the responsive nature of the website. The breakpoints that are set up for desktop, tablet, and mobile screens are usually determined by the theme, or possibly a page builder if you use one (e.g. Elementor, Beaver Builder, etc.), or maybe even WordPress itself if you’re using the default block editor.

It appears that you are just using the default block editor, and given the way you describe the issue, I think what you are up against is WordPress’s default breakpoints being at odds with how you want the columns to layout for each screen size.

Rather than using columns to layout your page, it is best to restrict the width of the content area and then just layout your content within that.

I’d recommend navigating to the WordPress theme customizer and clicking on the “Additional CSS” section. Add this rule to restrict the width of the content area only for pages using the Blank Slate template:

.page-template-blank-slate-template .type-page {
    width: 800px;
    margin: 0 auto;
    padding: 40px;
}

You can change the value for width as needed. Now, you can remove the columns from your page layout and let WordPress’s built-in breakpoints work for you, not against you.

• This reply was modified 3 years, 10 months ago by Micah Wood.

@salmanjaveed Yes, you can safely delete and reinstall the plugin without losing the data in post meta.

@salmanjaveed I’ve tested with the same WordPress version, PHP version, both the block editor and classic editor, with Elementor active… still not able to replicate the issue. Without a way to further help you debug, I’ll have to leave it up to you. It sounds like maybe it is a plugin conflict, but if you’re running the same plugins on a dev site, it may be an environmental difference. If you’re able to narrow it down, I’d be happy to try and replicate the issue again and see what I might be able to do to fix it.

@salmanjaveed I’m sorry, but I’m unable to replicate the issue you are having. Can you provide some more details? What version of WordPress are you running? Are you using the block editor or classic editor? Have you tried checking for plugin conflicts? (I recommend Plugin Detective).

The latest version (1.2.7) should resolve this for you.