mrjarbenne
Forum Replies Created
-
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] 4.3.1 memory errorI meant to come back and lost track of time. My server is already configured with a PHP memory limit of 256M, a time limit of 300 and a WordPress Memory Limit of 512M. It’s a solid state server with 32GB of RAM, which rarely gives me problems like this.
I do have 7500 blogs running on this subdomain network. Is it possible that JP is trying to run through an update of sorts and is failing? If I put the site in Development mode I can get to the settings panel, but regular mode results in those errors, and a white screen.
Not sure if that helps at all. Thanks @jeherve.
Forum: Plugins
In reply to: [WP Dashboard Notes] Feature Request: Allow Adding Notes on MobileI just figured if I sorted it out first, I’d send a pull request. Github isn’t a requirement for that though. If I sort out a tweak, I’ll post it here.
Cheers.
Forum: Plugins
In reply to: [WP Dashboard Notes] Feature Request: Allow Adding Notes on MobileYes. Editing an existing note definitely works. Thanks for looking into additional solutions for creating on mobile.
Is the project no longer on Github? I had seen you reference a link in another thread, but it’s not appearing on your Github profile.
Thanks Ryan. Much appreciated.
Back to the task at hand ;), here is the code we have been using up until now to customize Jetpack on our multisite install (https://commons.hwdsb.on.ca):
https://github.com/hwdsbcommons/block-jetpack/blob/master/class-umw-multisite-jetpack-control.php
This code worked fine in 4.2.2, but doesn’t hide the paid add ons within the security tab in 4.3.1.
With numerous bloggers under the age of 13, it’s important that we hide option to sign up for a wordpress.com account, and breach the terms of service. We enforce some modules on by default, enforce dev mode for students, and allow teaching staff to log in to their wp.com account via the other mu-plugins in that repo.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] 4.3.1 memory errorI’m seeing similar issues with 4.3.1. I can’t access the Settings page in Jetpack. It’s a blank screen.
[09-Sep-2016 02:57:51 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /wp-includes/wp-db.php on line 2399
[09-Sep-2016 02:58:26 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /wp-includes/meta.php on line 838Thanks Jeremy.
Forum: Plugins
In reply to: [BuddyPress Follow] Groups@mundial you can use the Invite Anyone plugin to get around this. It allows you to override the limitation of only being able to invite Friends, allowing you to deactivate the Friends component in lieu of the Follow plugin.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Post by Email Not WorkingI think we have this sorted out. My host was blocking xmlrpc calls.
Thanks for the consideration.
Forum: Plugins
In reply to: [BuddyPress Global Search] Illegal mix of collations Database ErrorThat’s awesome. Thanks so much for the support.
Forum: Plugins
In reply to: [BuddyPress Global Search] Illegal mix of collations Database ErrorBecause of the size and number of tables in my DB, I won’t be able to load them in the browser using phpmyadmin or adminer.
Since BuddyPress DB tables do not support uf8mb4, I would think that the search plugin should not assume that BP’s tables supports utf8mb4.
It’s been suggested to me that I could try using wp_encode_emoji() on the BP activity search string before using the content in a search, but I don’t have the chops to hack the plugin.
Thanks
Forum: Plugins
In reply to: [Broadcast] # mark in Blog Name corrupts Dashboard CSS rulesThanks. Doesn’t look like I’m able to update the forum post title. Sorry again about the mix up.
Cheers.
Forum: Plugins
In reply to: [Broadcast] # mark in Blog Name corrupts Dashboard CSS rulesForum: Plugins
In reply to: [Broadcast] # mark in Blog Name corrupts Dashboard CSS rulesYes, sorry. I had two different blogs. One called #now, and one called
<code>
. When I made the video to illustrate the issue, I realized that it was the<code>
site, not the #now site, that was causing the issue, and neglected to change the subject line of the support call. It’s the angle brackets, not the hashmark, that’s causing the issue.