jdjenkins
Forum Replies Created
-
Filter works great! I ended up just hardcoded the main blog name to avoid the switch_to_blog (which I already abuse too much). Thanks!
Forum: Plugins
In reply to: [Appointments] Appointments immediate moved to RemovedThe setting is set to 0. Changing it has no effect. I’ve tried uninstalling and reinstalling – but the data seemed to hang around in the database, as did this problem.
I’m going to uninstalling and go into the datatables and clear everything out. Will post results here.
Forum: Plugins
In reply to: [Stream] Network Stream: Access DeniedFrankie – Thanks for the response.
Unfortunately, commenting out these lines brought no change. I still receive the access denied/don’t have permissions to view the feed message for both RSS and JSON network-wide feeds.
@rreeve – This can be done using animate.css and wow.js to trigger the animations on scroll. It’s not terribly difficult, but it’s always preferable to include less plugins and external js when possible.
I second this (or third I suppose)! Having the animations trigger on scroll would be a killer feature.
Thanks ipstenu! Unfortunately, I’ve tried this variation (among other combinations of these settings). By including one or both of the first two lines (WP_ALLOW_MULTISITE and MULTISITE) I actually lose connection with the database for the entire install. “Error establishing database connection”
I’ve run a number of multisite installations in the past, but never one with an issue of this sort.
Sorry, the code that is not working is [su_tab title=”transfer students”]
Forum: Plugins
In reply to: [Genesis Simple Sidebars] Can no longer access Simple SidebarsRon –
Thanks for the response. My symptoms are the EXACT same as oise73.
And my server error log presents these errors ->
PHP Warning: Illegal string offset ‘name’ in ***/wp-content/plugins/genesis-simple-sidebars/includes/inpost.php on line 38
PHP Warning: Illegal string offset ‘name’ in ****/wp-content/plugins/genesis-simple-sidebars/includes/inpost.php on line 53Not those errors in the git issue you have linked.
The update to WordPress 3.8 – and the subsequent interface changes in the widgets screen – have made existing simple sidebars unclickable. I can change the css to remedy this, but it doesn’t fix the real issue. The names of the existing sidebars are not being printed and were not being printed prior to 3.8 update.
The same missing name or id of sidebars appears in the Simple Sidebars admin screen.
Forum: Plugins
In reply to: [Genesis Simple Sidebars] Can no longer access Simple Sidebarsoise73 – Ron seems to be ignoring my posting of the server errors I receive (which from the sound of things will be the exact errors you find). If your issue is resolved, please post the fix here! Thanks!
Forum: Plugins
In reply to: [Genesis Simple Sidebars] Can no longer access Simple SidebarsRon – I’m pretty certain that I’ve identified the issue. In inpost.php line 38 and 53 –
printf( '<option value="%s" %s>%s</option>', esc_html( $id ), selected( $id, genesis_get_custom_field( '_ss_sidebar_alt' ), false ), esc_html( $info['name'] ) );
throws an illegal string offset error in the latest versions of PHP… and so the name of the sidebar isn’t printed. From my limited PHP knowledge, it seems that one of these variables is a string rather than an array.Forum: Plugins
In reply to: [Genesis Simple Sidebars] Can no longer access Simple SidebarsSo, after installing the plugin on another site on the same server – it seems to work. So there’s something about the existing install on PHP 5.4 that’s not jiving.
I’ve tried re-installing, and hand erasing the data in ss-options with no luck.
Forum: Plugins
In reply to: [Genesis Simple Sidebars] Can no longer access Simple SidebarsI’m running into the same issue. I believe it’s caused by a conflict with PHP 5.4. Error log is throwing this –
PHP Warning: Illegal string offset ‘name’ in ***/wp-content/plugins/genesis-simple-sidebars/includes/inpost.php on line 38
PHP Warning: Illegal string offset ‘name’ in ****/wp-content/plugins/genesis-simple-sidebars/includes/inpost.php on line 53Any ideas on how to patch?