Title: Jamie O's Replies | WordPress.org --- # Jamie O [ ](https://wordpress.org/support/users/idealien/) * [Profile](https://wordpress.org/support/users/idealien/) * [Topics Started](https://wordpress.org/support/users/idealien/topics/) * [Replies Created](https://wordpress.org/support/users/idealien/replies/) * [Reviews Written](https://wordpress.org/support/users/idealien/reviews/) * [Topics Replied To](https://wordpress.org/support/users/idealien/replied-to/) * [Engagements](https://wordpress.org/support/users/idealien/engagements/) * [Favorites](https://wordpress.org/support/users/idealien/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 103 total) 1 [2](https://wordpress.org/support/users/idealien/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/idealien/replies/page/3/?output_format=md)… [5](https://wordpress.org/support/users/idealien/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/idealien/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/idealien/replies/page/7/?output_format=md) [→](https://wordpress.org/support/users/idealien/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Custom Login Page Customizer - Login Designer] Depecrated message](https://wordpress.org/support/topic/desecrated-message/) * [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [4 years, 4 months ago](https://wordpress.org/support/topic/desecrated-message/#post-15226357) * Similar error related to the use of wpmu_new_blog * PHP Deprecated: wpmu_new_blog is **deprecated** since version 5.1.0! Use wp_insert_site instead. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Loco Translate] Feature Suggestion – Switch language set when editing?](https://wordpress.org/support/topic/feature-suggestion-switch-language-set-when-editing/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [8 years, 11 months ago](https://wordpress.org/support/topic/feature-suggestion-switch-language-set-when-editing/#post-9171685) * **Related suggestion:** Being able to change b/t plugins would be great. Perhaps each element in the Title bar ( Plugins / WooCommerce / woocommerce-en_CA.PO ) could be a drop-down. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Idealien Rideshare] No rideshares available message](https://wordpress.org/support/topic/no-rideshares-available-message/) * Plugin Author [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [9 years, 7 months ago](https://wordpress.org/support/topic/no-rideshares-available-message/#post-8213673) * User test link confirms it has been resolved. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP-Post-Meta-Revisions] Meta Revisions being stored as arrays?](https://wordpress.org/support/topic/meta-revisions-being-stored-as-arrays/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [9 years, 11 months ago](https://wordpress.org/support/topic/meta-revisions-being-stored-as-arrays/#post-7088497) * Closing issue as it’s related to a separate plugin and how it is storing values within meta. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Gravity PDF] Output directory and template directory](https://wordpress.org/support/topic/output-directory-and-template-directory/) * [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 2 months ago](https://wordpress.org/support/topic/output-directory-and-template-directory/#post-6507480) * Has that been incorporated yet? * The last changelog for 3.7 mentions gfpdfe_template_location / gfpdfe_template_location_uri– but that is still an all or nothing. Doesn’t appear to address having the output folder in sub-folder of wp-content/uploads/ while the templates / config reside in a path defined via gfpdfe_template_location * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP Mail Logging] Multisite Attachments do not display](https://wordpress.org/support/topic/multisite-attachments-do-not-display/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 2 months ago](https://wordpress.org/support/topic/multisite-attachments-do-not-display/#post-7110191) * ``` ( [path] => /srv/www/example.dev/current/web/wp-content/uploads/sites/2/2016/02 [url] => http://example.dev/subsitename/wp-content/uploads/sites/2/2016/02 [subdir] => /2016/02 [basedir] => /srv/www/example.dev/current/web/wp-content/uploads/sites/2 [baseurl] => http://example.dev/subsitename/wp-content/uploads/sites/2 [error] => ) ``` * The other test indicates “Attachment: Is a file” * Now that I know the issue is not with the actual message, just the logging of it, I can work around the issue until a fix is available. I expect that if you setup a local site as a multisite environment you will experience the same issue which would be needed to develop / test. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP Mail Logging] Multisite Attachments do not display](https://wordpress.org/support/topic/multisite-attachments-do-not-display/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 2 months ago](https://wordpress.org/support/topic/multisite-attachments-do-not-display/#post-7110183) * Hey, * Using wp_mail directly, or through Gravity Forms, same result. I’ve tried with it in the WP_CONTENT directory and from the gravity_forms path inside the uploads folder. * The other thread you mention does reduce the scope of issue (that it must be in WP_CONTENT dir), but not resolve the issue itself. Here’s a snippet example– [http://pastebin.com/9Mc2eHaq](http://pastebin.com/9Mc2eHaq) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Nav Menu Roles] Conflict with WP Notification Centre](https://wordpress.org/support/topic/conflict-with-wp-notification-centre/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 3 months ago](https://wordpress.org/support/topic/conflict-with-wp-notification-centre/#post-7046714) * I cross-posted this on the other plugin support forum [https://wordpress.org/support/topic/conflict-with-nav-menu-roles-plugin-1](https://wordpress.org/support/topic/conflict-with-nav-menu-roles-plugin-1) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Gravity Forms + Custom Post Types] Populate custom field from taxonomy?](https://wordpress.org/support/topic/populate-custom-field-from-taxonomy/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 4 months ago](https://wordpress.org/support/topic/populate-custom-field-from-taxonomy/#post-6861806) * Initial solution for post type listing requires two changes. * 1) In gfcptaddon_1-5.php function render_editor_js extend the check of whether to display populate_with_post_type_field_setting based on field type to include post_custom_field. Current version that is line #223: * ``` if (field['type'] == 'select' || field['type'] == 'post_custom_field' ) { ``` * 2) In gfcptaddonbase.php function setup_form extend the list of checked field types to include post_custom_field. Current version that is line #61: * ``` if ($field['type'] == 'select' || $field['type'] == 'post_custom_field') { ``` * This support ticket would be resolved if this is incorporated into future release– or a more robust solution to account for use cases I’m not aware of. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Gravity Forms + Custom Post Types] Populate custom field from taxonomy?](https://wordpress.org/support/topic/populate-custom-field-from-taxonomy/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 4 months ago](https://wordpress.org/support/topic/populate-custom-field-from-taxonomy/#post-6861805) * Initial solution for taxonomy listing – In gfcptaddon_1-5.php function render_editor_js extend the list of valid_types array to include post_custom_field. Current version that is line #200: * ``` var valid_types = new Array('select', 'radio', 'checkbox', 'multiselect', 'post_custom_field'); ``` * Would benefit from some additional logic checking post_custom_field_type is a type that can include choices. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Import and export users and customers] Ability to update email for existing user](https://wordpress.org/support/topic/ability-to-update-email-for-existing-user/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 9 months ago](https://wordpress.org/support/topic/ability-to-update-email-for-existing-user/#post-6330741) * Can you provide an example spreadsheet of how one would take advantage of that? * Adding an extra ’email’ field did not resolve with 1.5.1 so far. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Loco Translate] Experimental – Core does not show up](https://wordpress.org/support/topic/experimental-core-does-not-show-up/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 11 months ago](https://wordpress.org/support/topic/experimental-core-does-not-show-up/#post-6225679) * I had to change from default language installation in order for it to be activated and show up. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Nav Menu Roles] Upgrade to 1.7.0 from 1.6.5 breaks core functionality](https://wordpress.org/support/topic/upgrade-to-170-from-165-breaks-core-functionality/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 11 months ago](https://wordpress.org/support/topic/upgrade-to-170-from-165-breaks-core-functionality/#post-6100404) * Correction – The above was when I took download .zip from Github that pulled master. Going to the releases tab to get the version you authored two days ago appears to be working as expected – limitations apply under logged in user selection, not everybody. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Nav Menu Roles] Upgrade to 1.7.0 from 1.6.5 breaks core functionality](https://wordpress.org/support/topic/upgrade-to-170-from-165-breaks-core-functionality/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [10 years, 11 months ago](https://wordpress.org/support/topic/upgrade-to-170-from-165-breaks-core-functionality/#post-6100403) * I have – and same result. * Expectation: 1. Open an existing menu item 2. Change display “Everyone” to “Logged In Users” 3. Limit logged in users to specific roles should still be visible and I select checkboxes to match my use case. 4. Click Save Menu 5. Settings are still saved * Actual Result: - Open an existing menu item - Change display from “Everyone” to Logged In Users” - The limit logged in users options no longer display. - If I change back to “Everyone” the checkboxes are still selected for limit logged in users - If I save Menu, the checkboxes are blanked out. * Rolling back to 1.6.5 again. Given that WP 4.3 is likely to move core Appearance > Menu to the customizer, I suspect you’ll have a large update coming that will need to support into this new approach as well to factor in. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Nav Menu Roles] Upgrade to 1.7.0 from 1.6.5 breaks core functionality](https://wordpress.org/support/topic/upgrade-to-170-from-165-breaks-core-functionality/) * Thread Starter [Jamie O](https://wordpress.org/support/users/idealien/) * (@idealien) * [11 years ago](https://wordpress.org/support/topic/upgrade-to-170-from-165-breaks-core-functionality/#post-6100348) * I see the options when I open up each menu item – the checkboxes / radio buttons/ etc – but the values do not save. * I didn’t test disabling other plugins / themes and to a certain extent, wouldn’t expect to have to, if the previous version of plugin worked with same combination of plugins / theme. The update to 1.7.0 was only one I made in that environment. I have since rolled back to 1.6.5 as I finish development of this site. * Will try against a fresh environment when I get cycles to and provide more feedback. Viewing 15 replies - 1 through 15 (of 103 total) 1 [2](https://wordpress.org/support/users/idealien/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/idealien/replies/page/3/?output_format=md)… [5](https://wordpress.org/support/users/idealien/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/idealien/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/idealien/replies/page/7/?output_format=md) [→](https://wordpress.org/support/users/idealien/replies/page/2/?output_format=md)