SuperCougar

OK Ron, thank you for answering.

Thanks a lot for the fix!

Hi Austin,

To help you understand the problem better, here is a link to a screen capture:

https://bit.ly/11vB9l9

Pending a fix, I have edited your “admin.css” file and commented out the “.wp-admin select” classe that way:

/* ---------- Fixes problem with Catalyst!
.wp-admin select {

	min-width: 150px;

}
---------- */

Hi Austin,

Thank you!

All problems are fixed now and Custom Login works like a charm.

Hi Austin,

Thank you for answering.

I’ll wait for next update for fixes.

I don’t know what you mean by “Did you run the update script?”. I just updated this plugin the usual way.

As for line breaks which are now automatically suppressed by WordPress in the custom CSS… too bad. I will work in a text file and then copy and paste.

Hi,

PHP Version: 5.3.17

WordPress Version: 3.5.1

Theme Version: Catalyst 1.5.4

Child Theme Version: Dynamik 1.1

The plugins I am using (all plugins are up to date):

01 – Akismet
02 – All in One SEO Pack
03 – cforms
04 – Content Switcher
05 – Custom Login lite
06 – Dynamic To Top
07 – Efficient Related Posts
08 – FD Feedburner Plugin
09 – Google Analyticator
10 – Google XML Sitemaps
11 – InfiniteWP – Client
12 – Lightbox Plus ColorBox
13 – Login With Ajax
14 – Peter’s Login Redirect
15 – Redirection
16 – Robots Meta
17 – SEO SearchTerms Tagging 2
18 – Simply Exclude
19 – Special Recent Posts FREE Edition
21 – Subscribe To Comments
21 – Table of Contents Creator
22 – TinyMCE Advanced
23 – W3 Total Cache
24 – Widget Logic
25 – WP Changes Tracker
26 – WP Maintenance Mode
27 – WPSubscribers
28 – XCloner

Hi Frank,

Everything is OK except the redirection. It doesn’t work for me.

Maybe there is something I don’t understand.

If I indicate for instance https://www.example.com/ I should be redirected to the home page of my site after logging in, in maintenance mode, which is not the case. I am still redirected to the dashboard.

It is not a real problem for me since I use another plugin to manage redirections after logging in (https://www.ads-software.com/extend/plugins/peters-login-redirect/) but anyway it was just to let you know.

Cordially

Hi Frank,

That is great ! Thank you very much for this update which is a good improvement.

There was a kind of misunderstanding between us, due to the fact that “wp-admin” is by default in the “Exclude” field. I didn’t pay attention to it and this is the reason why subscribers could go to the backend. So it was a mistake on my part.

Anyway, I think “wp-admin” shouldn’t be indicated there by default because it can be confusing.

Note that “Exclude” (without an “s”) would be better.

“Role Backend” should be “Backend Role” and similarly “Role Frontend” should be “Frontend Role”.

As for “Rewrite”, I think “Redirection” would be more understandable.

===

I am sorry to tell you that there still remains problems:

1) Problem #1 previously described is not fixed.

I am going to give you an example to try and make you understand:

1 – On a multisite installation, activate the plugin on the main blog and write “Test 01” in the “Text” field. Then deactivate the plugin on the main blog.

2 – Activate the plugin on the network.

You will see that “Test 01” is in the “Text” Field.

3 – Write something else, for instance “Test 02”, save and refresh the page.

>>> You will realize that “Test 01” appears again. And it is the same for every field.

So network-wide the plugin doesn’t memorize your custom data but the data of the main blog.

===

2) The “Rewrite” doesn’t work and the URL is not memorized in the field after saving and refreshing the page.

===

3) If you clear the “Exclude” field, save and refresh the page “Array” always reappears in the field.

Cordially

Hi,

Thank you for answering but I’m not any further ahead!

1 – I activated the plugin network wide, not in each blog.

So please, read my question #1 again.

2 – I am sorry to tell you that your English is very difficult to understand. You’d better write your answer in German and have it translated automatically, the result would be better.

I think you didn’t understand my request :

If I set the role to Administrator, non administrator users can still login and access the backend (Dashboard).

I do NOT want users go to the backend when my site is in maintenance mode.

So, you should add a second field to decide who can access the backend (as you did for the frontend).

See another plugin which does it here (Maintenance Mode):

https://www.ads-software.com/extend/plugins/maintenance-mode/screenshots/

Look a screenshot #4 (Plugin options, part 2) and you will see 2 fields:

1. Access to blog front-end with capability (role)

2. Access to blog administration / back-end with capability (role)

The second field is missing in your plugin.

I hope you’ll understand me better this time.

Cordially

Hi Alanft,

Excuse me for answering so late.

Your solution works like a charm.

Thanks a lot.