virgodesign

OK, thank you very much for this awesome plugin!

Hi, and thanks for the reply.
I’m running a wordpress multisite and I have a static subdomain where I put many libraries (with js and css files). This way I can Use these libraries in every subsite, independenlty from the activated theme. The plugin is not able to recognize the files inside this subdomain (due to the url path) and consider them as external.

Thanks to you Igor.

Yes but, in the $position parameter documentation there is a warning, as reported below:

WARNING: if two menu items use the same position attribute, one of the items may be overwritten so that only one item displays! Risk of conflict can be reduced by using decimal instead of integer values, e.g. 63.3 instead of 63 (Note: Use quotes in code, IE ‘63.3’).

And the Note suggest to quotes the decimal $position value.
Due to other plugins I was experience just this problem: I was not be able to se the the admin menu items. Quoting the $position param solve me the problem, showing the admin menu items correclty.

+1

Hi janis, sorry for the mistake!
Widgets appears correctly into the theme customizer.

Hi Mika,

I’ve just read your post
https://halfelf.org/2014/mapping-domains-without-plugin/

and you talk about COOKIE_DOMAIN as following:
define( ‘COOKIE_DOMAIN’, $_SERVER[ ‘HTTP_HOST’ ] );

So, what really happen if I wish to map a domain while above constants are defined?
IS there something that I can do to avoid conflicts, or simply I can’t define the constants if I map a domain?

Thank you very much in advance.

Hi Mika,

thanks for the reply, I did many tries to see how the system works and if everything works fine.

I noticed that defining these constants give an issue with the login cookies.
It seems that the problem comes out when login cookies expire.
The system logged me out and it can’t let me login again, bringing me (super_admin) into a login redirect loop.

The problem is with a subdomain, not with the main domain.
for example, when I attempt to login from

https://site.domain.com/wp-login.php

after authentication, I get redirect to

https://site.domain.com/wp-login.php?redirect_to=https://site.domain.com/wp-login.php&reauth=1

the login page reload asking me to authenticating again, and I can’t login anymore.

Disabling the constants, I’m able to login without any problem.

Did you have experience with this type of problem?
Thank you very much again.

Yes, my goal is to let a user to stay logged in both in their personal websites and in the main blog, so that when he woulds “signup for another blog” he don’t have to logs in again in the main website.

I think that both solutions could be fine.
Your first solution achives the goal, but we can get in possible security problems. Also, I noticed that a user see his frontend admin bar when he visits a stranger blog. That’s could get him in confusion.
Reason why I was thinking about second solution.

Let’s say that I’m trying to find the best solution to give users a perfect user-experience, without getting them in confusion.
That’s the reason why I was take in consideration more than one way.

Thank you very much for your help and excuse me for my not clean explanation ??

Hi Mika,

Maybe a more strong solution, instead of defining constants, could be forcing users to log in only from the main site (redirecting them to the main site login page, e.g. from site.domain.com/wp-login.php to https://www.domain.com/wp-login.php, solution here), and after a user logs in, redirect him to his primary blog dashboard, using the login_redirect filter.

What do you think about this?

Thank you very much again!

Hi Mika,

Thanks for the reply, I did some tries and it seems to works.

The only thing I noticed is that, with these constants defined, the wp_admin_bar will display everytime, even if I visit other subdomain websites.

Tha’t quite easy to solve but, in general, I wish to ask if defining these constants will involves in possible security problems.

Thank you very much.

The only solution I found, is to edit the core of wordpress.
I don’t remember exactly, but you can try to edit category-template.php file, that is wp-includes; both in lines 523 (inside the wp_tag_cloud) and 611 (wp_generate_tag_cloud) I changed ‘number’ => 45 with ‘number’ => 0

Excuse me but I’m not sure at 100%, you should try and let me know.

Thank you very much kgrantoz,

it works very good, both with posts and attachment images!

found a solution, hoping could be useful.

find and edit the following file:

/wordpress-form-manager/types/file.php

find the getFormattedFileName() function and before the last command (‘return $newFileName;’ ) insert a string replace command like this:

$newFileName = str_replace(" ","-",$newFileName);

this replaces blank spaces with “-“.

for me it works.
thanks

Hi Campbell,
is there a way to disable submit button during the submission process?
However it should return enabled if mandatory fields test fails.

any suggestions?

thankyou very much.