[Basem Aly]

Thank you, Ray. That was extremely helpful. I fixed it with a MySQL query.

[Basem Aly]

After digging around a bit, I realized that some users are identified by their username, while others are identified by their ID number. I’m not sure what’s causing the difference. It seems their user profiles have the same type of information. However, when I try to look at my user, for example, I can only access my profile using my ID number but not my username in the URL.

THIS WORKS- https://commons.pratt.edu/members/IDNUMBER/
THIS DOESN’T- https://commons.pratt.edu/members/USERNAME/

Any ideas on where I might look? Thank you.

[Basem Aly]

I think I’ve narrowed-down the problem of having the wrong server time for email digests. Under the “Group Email Subscription Options” page, I found this message:

“<i>The server timezone is UTC (UTC); the current server time is 3:10pm (15:10); and the day is Monday.”</i>

How would I change the timezone listed here?

Attachments:

You must be logged in to view attached files.

[Basem Aly]

After struggling for a few months trying to get LDAP to work for authentication, I ended up using Active Directory Integration. My bosses now want to revisit trying to use LDAP again. Can anyone suggest a plugin that might work? I had previously tried Simple LDAP (see my message above), but had no luck.

[Basem Aly]

Here’s what I found when I turned “Extended Profiles” back on. I turned on the Debugging Log and looked in the httpd-error log. There weren’t any errors in the Httpd-error log.

Here’s the output I got from the WP debug log. The first error refers to a custom plugin we created that lets us mass-import new users into a group. We had tested it previously and it didn’t cause an error when promoting/removing users.
<b>Strict Standards</b>: Declaration of Add_Pratt_User_To_BP_Group::display() should be compatible with BP_Group_Extension::display($group_id = NULL) in <b>/data/commonsdev/web/wp-content/plugins/pratt-bp-add-wp-user-to-group/pratt-bp-add-wp-user-to-group.php</b> on line <b>37</b>

<b>Strict Standards</b>: Declaration of ICE_File_Cache::add() should be compatible with ICE_Map::add($key, $value, $prepend = false) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/utils/file_cache.php</b> on line <b>133</b>

<b>Strict Standards</b>: Static function ICE_Style_Property::create() should not be abstract in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/dom/style.php</b> on line <b>825</b>

<b>Strict Standards</b>: Declaration of Infinity_Sections_Policy::instance() should be compatible with ICE_Policy::instance($class = NULL) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/api/sections.php</b> on line <b>23</b>

<b>Strict Standards</b>: Declaration of ICE_Option_Walker_Category::start_el() should be compatible with Walker_Category::start_el(&$output, $category, $depth = 0, $args = Array, $id = 0) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/components/options/walkers.php</b> on line <b>65</b>

<b>Strict Standards</b>: Declaration of ICE_Option_Walker_Category::end_el() should be compatible with Walker_Category::end_el(&$output, $page, $depth = 0, $args = Array) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/components/options/walkers.php</b> on line <b>65</b>

<b>Strict Standards</b>: Declaration of ICE_Option_Walker_Page::start_el() should be compatible with Walker_Page::start_el(&$output, $page, $depth = 0, $args = Array, $current_page = 0) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/components/options/walkers.php</b> on line <b>119</b>

<b>Strict Standards</b>: Declaration of ICE_Option_Walker_Page::end_el() should be compatible with Walker_Page::end_el(&$output, $page, $depth = 0, $args = Array) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/components/options/walkers.php</b> on line <b>119</b>

<b>Strict Standards</b>: Declaration of Infinity_Options_Policy::instance() should be compatible with ICE_Policy::instance($class = NULL) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/api/options.php</b> on line <b>23</b>

<b>Strict Standards</b>: Declaration of Infinity_Features_Policy::instance() should be compatible with ICE_Policy::instance($class = NULL) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/api/features.php</b> on line <b>23</b>

<b>Strict Standards</b>: Declaration of Infinity_Widgets_Policy::instance() should be compatible with ICE_Policy::instance($class = NULL) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/api/widgets.php</b> on line <b>23</b>

<b>Strict Standards</b>: Declaration of Infinity_Screens_Policy::instance() should be compatible with ICE_Policy::instance($class = NULL) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/api/screens.php</b> on line <b>33</b>

<b>Strict Standards</b>: Declaration of Infinity_Shortcodes_Policy::instance() should be compatible with ICE_Policy::instance($class = NULL) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/api/shortcodes.php</b> on line <b>23</b>

<b>Strict Standards</b>: Declaration of Infinity_Base_Walker_Nav_Menu::start_el() should be compatible with Walker_Nav_Menu::start_el(&$output, $item, $depth = 0, $args = Array, $id = 0) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/includes/walkers.php</b> on line <b>75</b>

<b>Strict Standards</b>: Declaration of Infinity_Base_Walker_Nav_Menu::end_el() should be compatible with Walker_Nav_Menu::end_el(&$output, $item, $depth = 0, $args = Array) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/includes/walkers.php</b> on line <b>75</b>

<b>Strict Standards</b>: Declaration of Infinity_Base_Walker_Page_Menu::start_el() should be compatible with Walker_Page::start_el(&$output, $page, $depth = 0, $args = Array, $current_page = 0) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/includes/walkers.php</b> on line <b>137</b>

<b>Strict Standards</b>: Declaration of Infinity_Base_Walker_Page_Menu::end_el() should be compatible with Walker_Page::end_el(&$output, $page, $depth = 0, $args = Array) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/includes/walkers.php</b> on line <b>137</b>

<b>Deprecated</b>: Non-static method ICE_Loader::load_wpadmin_lib() should not be called statically, assuming $this from incompatible context in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/ext/widgets/posts-list/class.php</b> on line <b>251</b>

<b>Strict Standards</b>: Declaration of ICE_Posts_List::single_row() should be compatible with WP_Posts_List_Table::single_row($post, $level = 0) in <b>/data/commonsdev/web/wp-content/themes/cbox-theme-1.0.7/engine/ICE/ext/widgets/posts-list/class.php</b> on line <b>259</b>

<b>Notice</b>: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in <b>/data/commonsdev/web/wp-includes/functions.php</b> on line <b>3457</b>

<b>Notice</b>: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in <b>/data/commonsdev/web/wp-includes/functions.php</b> on line <b>3457</b>

<b>Notice</b>: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in <b>/data/commonsdev/web/wp-includes/functions.php</b> on line <b>3457</b>

<b>Notice</b>: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in <b>/data/commonsdev/web/wp-includes/functions.php</b> on line <b>3457</b>

<b>Notice</b>: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in <b>/data/commonsdev/web/wp-includes/functions.php</b> on line <b>3457</b>

<b>Notice</b>: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in <b>/data/commonsdev/web/wp-includes/functions.php</b> on line <b>3457</b>

<b>Notice</b>: Undefined property: CBox_BP_Blogs_Recent_Posts_Widget::$option_name in <b>/data/commonsdev/web/wp-includes/widgets.php</b> on line <b>537</b>

<b>Warning</b>: array_merge(): Argument #2 is not an array in <b>/data/commonsdev/web/wp-includes/widgets.php</b> on line <b>1126</b>

<b>Strict Standards</b>: Declaration of BP_Groupemail_Extension::display() should be compatible with BP_Group_Extension::display($group_id = NULL) in <b>/data/commonsdev/web/wp-content/plugins/bp-group-email/includes/bp-group-email.php</b> on line <b>193</b>

<b>Strict Standards</b>: Declaration of BP_Groupemail_Extension::edit_screen() should be compatible with BP_Group_Extension::edit_screen($group_id = NULL) in <b>/data/commonsdev/web/wp-content/plugins/bp-group-email/includes/bp-group-email.php</b> on line <b>193</b>

<b>Strict Standards</b>: Declaration of BP_Groupemail_Extension::edit_screen_save() should be compatible with BP_Group_Extension::edit_screen_save($group_id = NULL) in <b>/data/commonsdev/web/wp-content/plugins/bp-group-email/includes/bp-group-email.php</b> on line <b>193</b>

<b>Strict Standards</b>: Declaration of BP_Groupemail_Extension::create_screen() should be compatible with BP_Group_Extension::create_screen($group_id = NULL) in <b>/data/commonsdev/web/wp-content/plugins/bp-group-email/includes/bp-group-email.php</b> on line <b>193</b>

<b>Strict Standards</b>: Declaration of BP_Groupemail_Extension::create_screen_save() should be compatible with BP_Group_Extension::create_screen_save($group_id = NULL) in <b>/data/commonsdev/web/wp-content/plugins/bp-group-email/includes/bp-group-email.php</b> on line <b>193</b>

<b>Strict Standards</b>: Declaration of BPGE::display() should be compatible with BP_Group_Extension::display($group_id = NULL) in <b>/data/commonsdev/web/wp-content/plugins/buddypress-groups-extras/core/loader.php</b> on line <b>1113</b>

[Basem Aly]

I finally tracked down the culprit that returns a blank screen whenever I try to promote or remove a member. It’s the “Extended Profiles” component of Buddypress. This is after updating all my plugins and disabling everything related to BB groups. Hopefully the “Extended Profiles” will be fixed soon.

[Basem Aly]

Thanks, but it doesn’t seem to have worked. I deactivated then deleted the Logout Redirect plugin, but I’m still getting the same white screen. Now in addition to the white screen when trying to promote/ demote members, I’m getting the white screen when trying to change a Group from Private to Public. Any more help would be greatly appreciated. Thanks.

[Basem Aly]

Oh cool. Thanks it worked when I removed the hyphen in the URL. It’s weird, however since if you use the ordinary group-creation menus and decide to add a blog to your group, then the blog takes your group name and replaces hyphens with spaces. How can you create a straight blog (without associated group) with hyphens in the URL?

[Basem Aly]

This is getting strange… I tried creating a site with some of the “Additional Privacy settings” and with “New Blog Templates” activated, and when I filled-in the site create form, It returned me to the same page without evidently doing anything. I tried it again with “New Blog Templates” disabled and got the same non-response, saying”There was a problem; please correct the form below and try again.”

Here’s yet another screenshot. It seems like site creation broke somehow. How can I troubleshoot this?

Attachments:

You must be logged in to view attached files.

[Basem Aly]

OK I disabled both “New Blog Templates” and reduced the “Additional Privacy Options” and I also disabled my cache plugin (WP Super Cache), and when the radio buttons worked; when I re-enabled the “New Blog Templates” plugin, the radio buttons still seem to be working. So this might be a cache issue, or something in “additional privacy options.” It still doesn’t explain why the privacy settings get split by the template selector. Is there a way for me to re-arrange that, or for me to add specific instruction text or otherwise consolidate the choices?

Attachments:

You must be logged in to view attached files.

[Basem Aly]

Looking at it again, it’s strange to me that the Privacy settings are split by the template selection appearing in between the Privacy settings radio buttons. Could this mean the “Blog Template” plugin might be interfering with the css for the privacy settings? I’ll disable blog templates and see how it affects the privacy settings.

Are other people using either “More Privacy Options” plugin along with the “NBlog Templates” plugin?

Attachments:

You must be logged in to view attached files.

[Basem Aly]

Hi, sorry I camping for a few days. The strange thing is the top 2 radio buttons under ” I would like my site to appear in search engines, and in public listings around this network. ” My mouse turns into the pointer icon, which means the browser recognizes it as a clickable entity, but nothing actually works.

Basically, I’d love some way to either remove those top radio buttons, or add my own explanation text and/ or default options.

[Basem Aly]

I’m still trying to figure out the best way to adjust the privacy options when setting up a new blog. I’m using the “More Privacy Options” plugin, but it seems the options conflict (or at least are confusing) with the privacy options above them (see the attached screenshot). What is the best way to remove the first set of options so that only the options from “More Privacy Options” appear? I’m also including a screenshot of the relevant site settings. Please suggest how I should set this to allow the full range of accessibility options.

Attachments:

You must be logged in to view attached files.

[Basem Aly]

It looks like it’s an issue with the theme I was using.

[Basem Aly]

Woohoo it was the Network site registration settings. Thanks, Scott!

[Author]

Posts