alpha.abcdefgh-dev.pw
alpha.abcdefg-hiet.cp
Two domain name has same length.
In wordpress, whole config, setting and plugin is store in wp_options.
So when I change domain name setting for FaceBook Authentication plugin named Gianism (a japanese WP plugin) I found that it work well on localhost.
But when I put it on live server abcdefgh-dev.pw, it not working. Thank God, after messing about 30 minutes I found that it caused by Serialize (or JSON) I've hardcoded in my Database:
...
login_url";s:36:"https://abcdefgh-dev.pw/login/";s:15:"after_login_url";s:30:"https://abcdefgh-dev.pw/";s:16:"after_logout_url";s:30:"https://abcdefgh-dev.pw/"
...
login_url";s:36:"https://abcdefgh-dev.pw/login/";
The s:36 as we know is the length of following string with length of 36 characters.
So when 2 above domain is same length and my local server work well, I was messed in live server not work.
Hope this help you in some case.
More about my situation is that:
I need deploy old server with Gianism plugin installed. As you know, without gianism correctly configured, you can't login to New server Admin to setting new server domain, App Id and App Secret of New Facebook app to make Gianism work.
So I need hardcode it in DB:
the wp_gianism_setting (or similar) in wp_options:
I find that it has API Key and App secret. So I hardcode new API key and secret to that. I also change new domain as above.
And new server .......... NOT WORK !
I need some more digging into source of Gianism, and frontend_user_admin(other WP plugin), a noddle file with around 8500K LOC in single file with PHP, HTML and more mixed. The problem with me is that I can't show Form for Login. Anh other way of show form didn't work ( I think because of access_token or crsf or other sercurity reason) that your inserted login form not work.
Gianism has one file that match the form login. And plugin loaded it over file called:
frontend_user_admin.php. After 1-2 day messing about this source, finally I found some line load thing that after load login form (step-login.php) ...
So I enable it (force enable over if(1) :)
then It work as normal.
alpha.abcdefg-hiet.cp
Two domain name has same length.
In wordpress, whole config, setting and plugin is store in wp_options.
So when I change domain name setting for FaceBook Authentication plugin named Gianism (a japanese WP plugin) I found that it work well on localhost.
But when I put it on live server abcdefgh-dev.pw, it not working. Thank God, after messing about 30 minutes I found that it caused by Serialize (or JSON) I've hardcoded in my Database:
...
login_url";s:36:"https://abcdefgh-dev.pw/login/";s:15:"after_login_url";s:30:"https://abcdefgh-dev.pw/";s:16:"after_logout_url";s:30:"https://abcdefgh-dev.pw/"
...
login_url";s:36:"https://abcdefgh-dev.pw/login/";
The s:36 as we know is the length of following string with length of 36 characters.
So when 2 above domain is same length and my local server work well, I was messed in live server not work.
Hope this help you in some case.
More about my situation is that:
I need deploy old server with Gianism plugin installed. As you know, without gianism correctly configured, you can't login to New server Admin to setting new server domain, App Id and App Secret of New Facebook app to make Gianism work.
So I need hardcode it in DB:
the wp_gianism_setting (or similar) in wp_options:
I find that it has API Key and App secret. So I hardcode new API key and secret to that. I also change new domain as above.
And new server .......... NOT WORK !
I need some more digging into source of Gianism, and frontend_user_admin(other WP plugin), a noddle file with around 8500K LOC in single file with PHP, HTML and more mixed. The problem with me is that I can't show Form for Login. Anh other way of show form didn't work ( I think because of access_token or crsf or other sercurity reason) that your inserted login form not work.
Gianism has one file that match the form login. And plugin loaded it over file called:
frontend_user_admin.php. After 1-2 day messing about this source, finally I found some line load thing that after load login form (step-login.php) ...
So I enable it (force enable over if(1) :)
then It work as normal.
Comments
Post a Comment