Plugin Directory

Changeset 3111147

Timestamp:
07/02/2024 12:38:22 PM (5 weeks ago)
Author:
whiteshadow
Message:

Version 1.12.3

Location:
admin-menu-editor/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • admin-menu-editor/trunk/menu-editor.php

    r3085980 r3111147  
    44Plugin URI: http://w-shadow.com/blog/2008/12/20/admin-menu-editor-for-wordpress/
    55Description: Lets you directly edit the WordPress admin menu. You can re-order, hide or rename existing menus, add custom menus and more.
    6 Version: 1.12.2
     6Version: 1.12.
    77Author: Janis Elsts
    88Author URI: http://w-shadow.com/blog/
  • admin-menu-editor/trunk/readme.txt

    r3108790 r3111147  
    55License: GPLv3
    66Requires at least: 4.7
    7 Tested up to: 6.5.3
    8 Stable tag: 1.12.2
     7Tested up to: 6.5.
     8Stable tag: 1.12.
    99
    1010Lets you edit the WordPress admin menu. You can re-order, hide or rename menus, add custom menus and more.
     
    7676
    7777== Changelog ==
     78
     79
     80
     81
     82
     83
     84
     85
     86
    7887
    7988= 1.12.2 =
     
    117126* Fixed a conflict with Toolset Types 3.4.7 that prevented redirect settings from being saved.
    118127* Fixed a PHP warning triggered when a menu item didn't have a URL or a required capability.
    119 * Fixed a plugin visibility bug where, if none of the user's roles had custom access settings for a specific plugin or in general, AME would immediatly deny access instead of also checking user capabilities. This could theoretically happen if all the user's roles were new or if the user didn't have any roles (they might still have access due to directly granted capabilities).
     128* Fixed a plugin visibility bug where, if none of the user's roles had custom access settings for a specific plugin or in general, AME would immediatly deny access instead of also checking user capabilities. This could theoretically happen if all the user's roles were new or if the user didn't have any roles (they might still have access due to directly granted capabilities).
    120129* Prevent a potential fatal error if JSON-encoded module settings stored in the database have been corrupted and can't be decoded.
    121130* Added some missing `.map` files that could cause 404 errors for users looking at the developer console.
Note: See TracChangeset for help on using the changeset viewer.