WordPress.org

Ready to get started?Download WordPress

Forums

All in One SEO Pack
[resolved] Please Move Setting Page Back Under Standard WordPress "Settings" (21 posts)

  1. DogsOfWar
    Member
    Posted 1 year ago #

    In the 2.0 release the settings page for AIOSEO has been moved to the very top of the sidebar in the WP dashboard. There's really not reason for this. Plugin settings belong in the WordPress "Settings" sidebar menu.

    It has become trendy for plugin developers to want their plugins front and center in the WP dashboard. I already installed your plugin, you don't need to convince me of anything else. Moving your plugin to such a prominent place serves no purpose. Imagine how busy the dashboard sidebar menu becomes when every plugin wants to do this. Make it stop.

    http://wordpress.org/extend/plugins/all-in-one-seo-pack/

  2. p.law
    Member
    Posted 1 year ago #

    Seriously. And plugins that create their own additional update notifications. This is why we have hierarchical menus -- to keep every little thing from competing for your attention and organized logically.

  3. Frank Goossens
    Member
    Posted 1 year ago #

    absolutely, please revert!

  4. Frank Goossens
    Member
    Posted 1 year ago #

    for those interested; you can at least already move aioseo down the menu by opening aioseop_class.php and comment out line 1655;

    // add_filter( 'custom_menu_order', '__return_true' );
  5. Bernhard
    Member
    Posted 1 year ago #

    @ futtta,
    thank you for this hack!

    But i second the request to move the settings page for AIOSEO back to "Settings" without any hack!

  6. Bernhard
    Member
    Posted 1 year ago #

    As futtta has given the right information, I now have commented out lines 1652 to 1656:

    function admin_menu() {
    		$file = plugin_basename( __FILE__ );
    /*		$menu_name = __( 'All in One SEO', 'all_in_one_seo_pack' );
    		add_menu_page( $menu_name, $menu_name, 'manage_options', $file, Array( $this, 'display_settings_page' ) );
    		add_meta_box('aioseop-about', "About <span style='float:right;'>Version <b>" . AIOSEOP_VERSION . "</b></span>", array( $this, 'display_side_metaboxes'), 'aioseop_metaboxes', 'side', 'core');
    		add_filter( 'custom_menu_order', '__return_true' );
    		add_filter( 'menu_order', array( $this, 'set_menu_order' ) ); */

    Like this the settings page is still available by "Plugins" => "Options configuration panel".

    Seems to be the best solution as long as this bug isn't fixed.

    Thank you again @futtta!

  7. PayBas
    Member
    Posted 1 year ago #

    I second this

  8. adventurenick
    Member
    Posted 1 year ago #

    I'd agree also - it was perfect where it was before, but if by default you really want it out of the settings menu and more in the open, it should go beneath the settings menu like all of the other plugins that show up in the sidebar do like W3TC, WordFence, etc... SEO is important, but it doesn't belong at the very top of the admin sidebar.

  9. DogsOfWar
    Member
    Posted 1 year ago #

    I definitely appreciate the great detective work to track down the offending code, but this level of manipulation shouldn't be necessary.

    I see that the plugin author has commented on nearly every post here and is very active in providing support which is outstanding. But that makes the lack of comment here all the more glaring. If he would care to explain the reasoning I'd gladly listen and give feedback.

  10. asocalguy
    Member
    Posted 1 year ago #

    This seems like pure hubris by the designer, Michael Torbert, and kind of a d-bag move. There's nothing about AIOSEO's settings that require breaking the WordPress menu convention to put his plugin in such a prominent location in the menu. Looks like it's time to go check out WordPress SEO from Yoast.

  11. Michael Torbert
    WordPress Virtuoso
    Plugin Author

    Posted 1 year ago #

    Thanks for the feedback everyone, especially those that weren't unnecessarily rude about a free plugin I've spent over 5 years developing and supporting.
    We'll release an update soon that lets the menu item be moved down for those that need it.

  12. DogsOfWar
    Member
    Posted 1 year ago #

    I saw that 2.0.1 was available and loaded it up thinking that might have the option that was mentioned to demote the plugin's settings page. I don't see that option, but what I do see is now the addition of an AIOSEO page added to the floating WordPress admin bar at the top of all of my WP pages. That's pretty much the opposite of what I was hoping for.

    Honestly, the plugin works fine and I'm able to enter meta information easily on the posts themselves. After installing the plugin the first time and getting the settings the way I need them I don't see why I need such ready access to the settings for this plugin. The plugin does a nice job of being "set it and forget it" as far as settings go.

  13. wpsmort
    Member
    Posted 1 year ago #

    Hi DogsOfWar,

    Go to General Settings in All in One SEO Pack, scroll down to the Display Settings box and you will see the checkboxes there where you can disable AIOSEOP on the Admin Bar and demote the side menu item to the bottom.

  14. DogsOfWar
    Member
    Posted 1 year ago #

    Thanks, somehow I missed those. Settings updated.

    However, what that does is move the same menu down further on the sidebar. Definitely an improvement, but what I was asking for was that the plugin store its settings nested under the standard WordPress Settings sidebar menu (where 90% of all plugins drop their settings pages and where they don't clutter up the sidebar).

  15. Grace Massa Langlois
    Member
    Posted 1 year ago #

    Hmm I guess I'm in the minority, I really liked that it was moved.

  16. Bernhard
    Member
    Posted 1 year ago #

    As the author of AIOSEO doesn't seem to be interested in fixing the bugs that occurred since v2.x I've tested a lot of SEO plugins now.

    My favorites are Greg's High Performance SEO and HeadSpace2 SEO.

    In my opinion AIOSEO up to v2.x has been better than both of the above mentioned.

    Today I started to switch all my WordPress instances to HeadSpace2.

  17. Michael Torbert
    WordPress Virtuoso
    Plugin Author

    Posted 1 year ago #

    Bernhard:
    We're very interested in fixing bugs.
    Can you be specific about the bugs you're referring to?

  18. AITpro
    Member
    Posted 1 year ago #

    @Michael T - yeah man doesn't matter how much blood, sweat, tears and years you put into it, how awesome your plugin is, how much folks have benefited from your AWESOME plugin, including myself - you will always have a handful of folks nickel and dime you to death. I think the old ancient philosophy about not using Top Level menus is well...ancient and outdated. Out with the old and in with the new I always say.

    Keep on rockin it man! All in One SEO kicks A$$! Thank you.

  19. asocalguy
    Member
    Posted 11 months ago #

    @Michael Torbert: I'll admit that my "hubris" and "d-bag" comments were harsh and uncalled for and I apologize for them. I have to say though that the changes in menu placement that you made to your plugin that you "spent over 5 years developing and supporting" also broke two WordPress Multisite sites that I've run for clients for years. It created headaches for me and expense for them. Obviously plugin changes are to be expected and can break sites from time to time. At the same time, as I'm sure you know well, WordPress' design "standards" help to prevent these things from happening. So moving your plugin's UI to the top menu was confusing to the users, broke code design to manage and simplify the menus and was generally unnecessary since most of those settings would be accessed infrequently. Not to mention, this change was not clearly stated in the change log for v2.0. I appreciate that you have developed a popular plugin and want to do so in your own way but making a change like this (which seems inconsequential) has repercussions for your users.

  20. Michael Torbert
    WordPress Virtuoso
    Plugin Author

    Posted 11 months ago #

    @asocalguy

    A better course of action would have been to have submitted a bug report with the specifics of the issue you're seeing.
    We've tested on multisite, and have many multisite users. This is the first I'm hearing of any issues. It sounds like you've made some customizations to the menu that have a conflict with AIOSEOP.
    Either way, let us know exactly what's going on and I'll fix any bugs.

  21. asocalguy
    Member
    Posted 11 months ago #

    Thanks for your reply, Michael. It's not a bug, per se, so we didn't report it as such. We have custom code that (among other things) controls what options show up to the end users by altering the array of Settings menu items. When AIOSEOP moved, this code broke and the end users started tinkering, asking questions, etc. in addition to it causing a few other things to not work. I won't go into details because it's not a bug; it works as you expect it to.

    My main issue is the fact that AIOSEOP went from (appropriately) being another plugin in the Settings menu to being the most prominent item in the menu after the Dashboard (even more prominent than core features people use every day!) and also/redundantly on the admin menu across the top of the window. This makes no sense to me as the three options under this menu will probably be used rarely once they are tuned and could have easily been handled as tabs within your settings page. It would have made much more sense to leave AIOSEOP under the Settings menu and give the user the option to promote it to the top level if they wanted it there. There's no way to know for certain, of course, but I would bet NO ONE would choose to move your menu item to the top level if they had been given that choice.

    Frankly, the only way the move makes sense to me is if it's an attempt to get your Hostgator and Headway Themes affiliate banners in front of more users and promote more donations and Amazon Wishlist purchases and that doesn't really seem to fit the WordPress ethos.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic