Marat Nepomnyashy

Ah, I see, you want to redirect the users to a custom URL rather than the ‘wp-login.php’ URL. That’s not supported, but you can implement an alternative login page in several ways. You can either (1) customize ‘wp-login.php’ to look like the page you want, similar to how described at https://premium.wpmudev.org/blog/customize-login-page/ or (2) you can tweak the plugin instance on your site to redirect to another URL by modifying this line https://github.com/maratbn/LoginRequirePress/blob/master/loginrequirepress/LoginRequirePress.php#L198 or (3) You can hook into the WordPress filter ‘login_url’ — https://developer.www.ads-software.com/reference/hooks/login_url/ and change it to redirect to the URL you want rather than ‘wp-login.php’

Hello,

When the user hits a page that requires login to view, the plugin should redirect to ‘wp-login.php’, not ‘wp-admin’. Once the user logs in on ‘wp-login.php’, plugin will redirect the user back to the page they attempted to view before they logged in.

It is not clear what exactly you mean by “front login”, but if you’re asking to redirect the user to the front page either instead of the login page, or after the user logs in, that is not supported.

However, when ‘wp-login.php’ renders, it does include a link back to the home page below the login box that says “<- Back to [site name]”.

OK, thanks for the info. There could definitely be a UI to simultaneously apply meta tokens to multiple posts. How many posts do you have on your WP site?

Hello,

I think you’re asking if it is possible to specify certain robots meta tags for multiple pages at once based on certain page criteria, such as page URL.

This is currently not possible with this plugin. This plugin currently requires that the robots meta tags be specified individually for each separate page / post.

As far as targeting pages that contain ‘index.php’ in their URL, all posts on a WP site can be accessible via a URL with ‘index.php’ spelled out; however, most WP sites use permalink settings that allow posts to be accessed by URLs containing their slugs, and such URLs are more convenient because they are more descriptive.

I’m not aware of any WP plugins that allow specifying robots meta tags for multiple pages at once. If you come across any please write. What is that Joomla plugin you were using?

As I think about it, perhaps there could be a mechanism to specify robots meta tags for multiple posts based on post tags or categories. I’ll digest that thought, and in the meantime, patches and pull requests welcome.

— Marat

Thank you for the positive review. Glad it’s working for you!

— Marat

Hello,

From this parse error, it appears that your PHP environment does not support the PHP short array syntax.

This syntax is supported since PHP >= 5.4 Which PHP version are you running?

You can install this plugin to find out:

https://www.ads-software.com/plugins/display-php-version/

From your description it appears you have a nested WordPress install, and those were not supported properly in the version 1.1.0 and prior, due to a bug that you just discovered. Thank you for that.

I just fixed this bug and released new version 1.2.0 that does support nested installs. So try it again with this just-released version, and let me know how it works.

BTW, seeing the slash after ‘index.php’ gets me curious. Is ‘index.php’ a hierarchy name on your site?

The crux of this problem is that WordPress does not currently support PHP minimum version enforcement for themes and plugins.

https://core.trac.www.ads-software.com/ticket/23880

There is already a version test in the logic, but PHP <= 5.3 errors-out before it can be reached.

Work-arounds for that would add a slight performance penalty for each HTTP request to the site, which is just not worth it for the vast majority of users running some more recent PHP.

Hello, this plugin requires PHP >= 5.4

https://github.com/maratbn/RobotsWhiz/blob/master/REQUIREMENTS

I just noticed that this information is not displayed at https://www.ads-software.com/plugins/robotswhiz/ so I’m planning to update that with the next release.

Are you using PHP >= 5.4?

If you’re not sure try using this plugin to find out:

https://www.ads-software.com/plugins/display-php-version/

Hmmmm…

You mean blank screen, right?

Are you seeing the 2 ‘Update LR Settings’ buttons one on top and one below?

You do not see any table rows at all, right?

Do you have pages / posts on your site?

What version of WordPress are you running? What version of PHP? You can use this plugin to determine PHP version — https://www.ads-software.com/plugins/display-php-version/

Are you able to view the Apache error log for your website and see if it gets any errors / warnings when you refresh the settings page?

Which browser are you seeing this in? Does the problem persist if you use a different browser?

— Marat

This issue is now tracked here:

https://github.com/maratbn/LoginRequirePress/issues/3

As of version 0.1.2, any search result pages containing login-protected posts no longer require user login to view, and the titles and contents of the login-protected posts are protected within the search results.

This plugin is free and open-source software.

That means 2 things — 1 — it is available free of charge for the benefit of humanity and for all the decent people out there to make their lives a little easier, and 2 — the entire source is available to the user, so whoever has it can modify it on their server any way they like, and even send a patch upstream to contribute themselves.

But for any users out there in the larger scope of the word, only looking to use other peoples’ work, and then give nothing back in return but to smear the work down to 3 stars in the course of some passive-aggressive strategy to get some new feature implemented that they really want, rather than contribute back to the project in a true open-source fashion, I have a message for you:

I DON’T WANT YOU AS A USER.

Since you made the changes in the WordPress theme customizer, it makes me suspect that it is the WordPress logic outside of this plugin that made your current theme look different.

Will the problem still persist if you uninstall this plugin? If so, then it’s not this plugin’s fault, as it is intended to augment to rather than change the WordPress default behaviour.