53 points
Community rank #1138
enkreativbyra
VeteranJust Getting Started
MemberLikes (0)
Hi!
I cant access the admin panel with the mapped domain (mapped.lo instead of site1.demo.lo). The site1.demo.lo works in the backend though.
When I try to login (mapped.lo/login) the code below appears.
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Warning: Cannot modify header information - headers already sent by (output started at /*SITELOCATION*/wp-includes/functions.php:3071) in /*SITELOCATION*/wp-login.php on line 365
Warning: Cannot modify header information - headers already sent by (output started at /*SITELOCATION*/wp-includes/functions.php:3071) in /*SITELOCATION*/wp-login.php on line 377
Warning: Cannot modify header information - headers already sent by (output started at /*SITELOCATION*/wp-includes/functions.php:3071) in /*SITELOCATION*/wp-includes/pluggable.php on line 680
Warning: Cannot modify header information - headers already sent by (output started at /*SITELOCATION*/wp-includes/functions.php:3071) in /*SITELOCATION*/wp-includes/pluggable.php on line 681
Warning: Cannot modify header information - headers already sent by (output started at /*SITELOCATION*/wp-includes/functions.php:3071) in /*SITELOCATION*/wp-includes/pluggable.php on line 682
Notice: Undefined index: HTTPS in /*SITELOCATION*/files/apps/domain-mapping/domain-mapping.php on line 746
Warning: Cannot modify header information - headers already sent by (output started at /*SITELOCATION*/wp-includes/functions.php:3071) in /*SITELOCATION*/wp-includes/pluggable.php on line 881
It works fine to access the frontend and it redirects to the mapped domain, but it shows the following notices:
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined index: HTTPS in /*SITELOCATION*/files/apps/domain-mapping/domain-mapping.php on line 746
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
And finally, when I try to access the admin section (mapped.lo/wp-admin/) it shows following:
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Notice: Undefined property: stdClass::$blog_id in /*SITELOCATION*/wp-includes/functions.php on line 3071
Warning: Cannot modify header information - headers already sent by (output started at /*SITELOCATION*/wp-includes/functions.php:3071) in /*SITELOCATION*/wp-includes/pluggable.php on line 881
Lot of code there, but I hope it will be helpfull!
53 pointsCommunity rank #1138VeteranJust Getting Started
Member
(joined August 2011)
Likes (0)
Hi!
Tried a fresh set of files and cleared all files and databases.
Still the same problem. Have tried all settings for administration area, but no luck. And I want it to be the domain set up by the user to be used as administration.
No highlighted areas what I can see, So I guess I've done all tasks, followed the installation guide.
Any other ideas? Tried the original WP domain mapping and it did work better, but lacks some of the functionality that yours have. At the moment I'm looking into merging the two for a working solution.
53 pointsCommunity rank #1138VeteranJust Getting Started
Member
(joined August 2011)
Likes (0)
So it seems like it's this snippet in wp-includes/functions.php
/**
* Is main site?
*
*
* @since 3.0.0
* @package WordPress
*
* @param int $blog_id optional blog id to test (default current blog)
* @return bool True if not multisite or $blog_id is main site
*/
function is_main_site( $blog_id = '' ) {
global $current_site, $current_blog;
if ( !is_multisite() )
return true;
if ( !$blog_id )
$blog_id = $current_blog->blog_id;
return $blog_id == $current_site->blog_id;
}
that creates all the errors.
That and the following snippet in domain-mapping.php:
53 pointsCommunity rank #1138VeteranJust Getting Started
Member
(joined August 2011)
Likes (0)
Hi again,
Sorry to post so many problems, but I need some pointers.
The backend only shows errors if I use either mapped or user-entered domain - original is fine. Still shows a lot of notices about blog_id though.
It seems the Domain Mapping makes some plugin stop working on the front end.
Also, I can't use the WPML plugin in certain ways with the Domain Mapping. It does not work if I add /en/ as a different catalog. But it does work if I use the ?lang= en parameter.
2944 pointsCommunity rank #20Supreme DeityMind-Blowingly HelpfulLifetime member
DEV Diva
(joined February 2012)
Likes (0)
Hope you're well @enkreativbyra
Just checking in on behalf of @KimberlyL to see if there is anything else that we can assist with. Did you get sorted or are there still issues outstanding that needs to be addressed?
Since it's been a while that we last heard from you, I will go ahead and resolve this topic, but please don't hesitate to reopen it should you still require additional support from us. Just select the 'Mark as Not Resolved (re-open)' box below the post area (otherwise we might miss your new post).
50 pointsCommunity rank #1213VeteranJust Getting Started
Member
(joined December 2011)
Likes (0)
Hello,
it's a little bit old, but not resolved yet and I just had this problem, too.
Here's the fix - please contact the plugin author, that he adds these lines into sunrise.php around line 50:
if ( ! isset( $current_site->blog_id ) )
$current_site->blog_id = $wpdb->get_var( $wpdb->prepare( "SELECT blog_id FROM $wpdb->blogs WHERE domain = %s AND path = %s", $current_site->domain, $current_site->path ) );
By the way please tell the plugin author that he please replaces all URLs with 'wp-content/'... with the constant WP_CONTENT_URL in domain-mapping.php
Thanks,
Fee
50 pointsCommunity rank #1213VeteranJust Getting Started
Member
(joined December 2011)
Likes (0)
in Domain Mapping version 3.1.1 these errors are still present (in debugging mode of course). The code I mentioned removes them. Is there a reason why the plugin author didn't take a look at it?
Sure I could ignore the errors, but there are bugs without debugging mode. Should I open new tickets for that?
For example, subsites with mapped domains show this message in admin:
"BuddyPress was successfully activated! Please run the installation wizard."
It seems that the Buddypress network of the mainsite is not recognized. This problem is solved with my mentioned code, too.
new errors in version 3.1.1 (additional and not solved with my code snippet):
Notice: Trying to get property of non-object in .../plugins/domain-mapping/classes/class.domainmap.php on line 566
Warning: Missing argument 2 for wpdb::prepare(), called in .../plugins/domain-mapping/classes/class.domainmap.php on line 857
Warning: Missing argument 2 for wpdb::prepare(), called in .../plugins/domain-mapping/classes/class.domainmap.php on line 1040
6950 pointsCommunity rank #8Supreme DeityWPMU DEV StaffLifetime member
Developer
(joined June 2008)
Likes (0)
I'm not getting any of the errors you are reporting on my install - which is concerning. Can you give me some details about the versions of WP and Buddypress you are running and I'll try to replicate your set up.
50 pointsCommunity rank #1213VeteranJust Getting Started
Member
(joined December 2011)
Likes (0)
Hello Barry, thanks for your reply!
I started facing this issue with WP 3.4.2 and BP 1.5.1 on a new install and updated both from time to time, tested BP 1.6, too. Currently I'm on WP 3.5 RC1 and BuddyPress trunk 6536. On local server, but I had problems on remote server, too (but there not experimenting...).
Apache 2.2.22
PHP 5.3.15 with Suhosin-Patch
MySQL 5.1.58
50 pointsCommunity rank #1213VeteranJust Getting Started
Member
(joined December 2011)
Likes (0)
Hello Barry,
I updated to your new version 3.1.2 with your fix and wanted to give you feedback that it's working good! Nearly all errors disappeared, all urls are working correctly, no BuddyPress notice anymore. :-)
Only the error Warning: Missing argument 2 for wpdb::prepare(), called in .../plugins/domain-mapping/classes/class.domainmap.php on line 1040
is still there. It disappears if I change line 1040 to: $olddomain = $this->db->get_var( $this->db->prepare( "SELECT option_value FROM %s WHERE option_name='siteurl' LIMIT 1 /* domain mapping */", $this->db->options ) );
And the notice (in admin only) Notice: Trying to get property of non-object in .../plugins/domain-mapping/classes/class.domainmap.php on line 566
disappears if I change line 566 to: $key = get_user_meta($user['ID'], 'cross_domain', true);
Thanks for your plugin, it's really great work!
6950 pointsCommunity rank #8Supreme DeityWPMU DEV StaffLifetime member
Developer
(joined June 2008)
Likes (0)
This is fixed in the release I have ready to go a little bit later with updates so we are ready for when WP 3.5 drops. Keep an eye on the update notifications.
Responses (15)
People Person (joined February 2012) Likes (0)
Hi there!
Sorry you are having trouble here.
Have you tried to deactivate all plugins minus the Domain Mapping ot see if this is a conflict issue?
Also, what are your settings on The domain used for the administration area should be the
Do you have the highlighted area on your Domain Mapping plugin Menu? If so have you done all it asks?
(I've not completely set mine up yet, just installed for testing, so please disregard if you have completed all of those instructions)
Best,
Kimberly
Member (joined August 2011) Likes (0)
Hi!
Tried a fresh set of files and cleared all files and databases.
Still the same problem. Have tried all settings for administration area, but no luck. And I want it to be the domain set up by the user to be used as administration.
No highlighted areas what I can see, So I guess I've done all tasks, followed the installation guide.
Any other ideas? Tried the original WP domain mapping and it did work better, but lacks some of the functionality that yours have. At the moment I'm looking into merging the two for a working solution.
Thanks!
Member (joined August 2011) Likes (0)
Tried back and fourth with both plugins now and it seems like the wpmu version is the one that works best actually, for me anyways.
If I disable the wp_debug everything runs smoothly. But thats not really the way to go, I want it to work like a charm with wp_debug on as well :)
Member (joined August 2011) Likes (0)
So it seems like it's this snippet in wp-includes/functions.php
that creates all the errors.
That and the following snippet in domain-mapping.php:
$protocol = ( 'on' == strtolower( $_SERVER['HTTPS' ] ) ) ? 'https://' : 'http://';What can I do to fix these?
Please help!
Member (joined August 2011) Likes (0)
Hi again,
Sorry to post so many problems, but I need some pointers.
The backend only shows errors if I use either mapped or user-entered domain - original is fine. Still shows a lot of notices about blog_id though.
It seems the Domain Mapping makes some plugin stop working on the front end.
Also, I can't use the WPML plugin in certain ways with the Domain Mapping. It does not work if I add /en/ as a different catalog. But it does work if I use the ?lang= en parameter.
Anyone smart out there, please?
People Person (joined February 2012) Likes (0)
Sorry about the delay, the weekend tends to break things up sometimes.
My original response was meant to have a picture attached, oops!
:)
Which plugins? Are you testing them with domain mapping off as well to confirm?
I'll ask the developer to stop by an comment on your WPML issue.
DEV Diva (joined February 2012) Likes (0)
Hope you're well @enkreativbyra
Just checking in on behalf of @KimberlyL to see if there is anything else that we can assist with. Did you get sorted or are there still issues outstanding that needs to be addressed?
Since it's been a while that we last heard from you, I will go ahead and resolve this topic, but please don't hesitate to reopen it should you still require additional support from us. Just select the 'Mark as Not Resolved (re-open)' box below the post area (otherwise we might miss your new post).
All the best!
Gina
Member (joined December 2011) Likes (0)
Hello,
it's a little bit old, but not resolved yet and I just had this problem, too.
Here's the fix - please contact the plugin author, that he adds these lines into sunrise.php around line 50:
By the way please tell the plugin author that he please replaces all URLs with 'wp-content/'... with the constant WP_CONTENT_URL in domain-mapping.php
Thanks,
Fee
Member (joined December 2011) Likes (0)
for reference, I came upon this solution here: http://core.trac.wordpress.org/ticket/22090#comment:13
Member (joined December 2011) Likes (0)
in Domain Mapping version 3.1.1 these errors are still present (in debugging mode of course). The code I mentioned removes them. Is there a reason why the plugin author didn't take a look at it?
Sure I could ignore the errors, but there are bugs without debugging mode. Should I open new tickets for that?
For example, subsites with mapped domains show this message in admin:
"BuddyPress was successfully activated! Please run the installation wizard."
It seems that the Buddypress network of the mainsite is not recognized. This problem is solved with my mentioned code, too.
new errors in version 3.1.1 (additional and not solved with my code snippet):
Notice: Trying to get property of non-object in .../plugins/domain-mapping/classes/class.domainmap.php on line 566
Warning: Missing argument 2 for wpdb::prepare(), called in .../plugins/domain-mapping/classes/class.domainmap.php on line 857
Warning: Missing argument 2 for wpdb::prepare(), called in .../plugins/domain-mapping/classes/class.domainmap.php on line 1040
Developer (joined June 2008) Likes (0)
I'm not getting any of the errors you are reporting on my install - which is concerning. Can you give me some details about the versions of WP and Buddypress you are running and I'll try to replicate your set up.
Member (joined December 2011) Likes (0)
Hello Barry, thanks for your reply!
I started facing this issue with WP 3.4.2 and BP 1.5.1 on a new install and updated both from time to time, tested BP 1.6, too. Currently I'm on WP 3.5 RC1 and BuddyPress trunk 6536. On local server, but I had problems on remote server, too (but there not experimenting...).
Apache 2.2.22
PHP 5.3.15 with Suhosin-Patch
MySQL 5.1.58
Member (joined December 2011) Likes (0)
Hello Barry,
I updated to your new version 3.1.2 with your fix and wanted to give you feedback that it's working good! Nearly all errors disappeared, all urls are working correctly, no BuddyPress notice anymore. :-)
Only the error
Warning: Missing argument 2 for wpdb::prepare(), called in .../plugins/domain-mapping/classes/class.domainmap.php on line 1040
is still there. It disappears if I change line 1040 to:
$olddomain = $this->db->get_var( $this->db->prepare( "SELECT option_value FROM %s WHERE option_name='siteurl' LIMIT 1 /* domain mapping */", $this->db->options ) );And the notice (in admin only)
Notice: Trying to get property of non-object in .../plugins/domain-mapping/classes/class.domainmap.php on line 566
disappears if I change line 566 to:
$key = get_user_meta($user['ID'], 'cross_domain', true);Thanks for your plugin, it's really great work!
Developer (joined June 2008) Likes (0)
This is fixed in the release I have ready to go a little bit later with updates so we are ready for when WP 3.5 drops. Keep an eye on the update notifications.
Support Chimp (joined March 2010) Likes (0)
Hey again.
Haven't heard from you in a short while so I just wanted to check in and see how things are going here?
If you still need some assistance then by all means just reopen the thread or create another one for any new and related issues.
Take care.
WordPress Questions?
We've got answers!
Find out more »