Plugin Directory

Changeset 802754


Ignore:
Timestamp:
11/11/2013 09:53:16 PM (12 years ago)
Author:
mfisc
Message:

basic plugin structure and wp sites integrations

Location:
log-viewer
Files:
14 added
2 deleted
3 edited

Legend:

Unmodified
Added
Removed
  • log-viewer/branches/rewrite/readme.txt

    r801627 r802754  
    66Requires at least: 3.4
    77Stable Tag: 13.11.09
    8 Latest Version: 13.11.09-1728
     8Latest Version: 13.11.11-2248
    99License: GPLv2 or later
    1010License URI: http://www.gnu.org/licenses/gpl-2.0.html
     
    1919
    2020To activate Wordpress logging to file you have to set `define( 'WP_DEBUG_LOG', true );` in your wp-config.php file.
     21In Multisite installations you have to be Super Admin for using this plugin.
     22Additionally inn Singlesite installations you have to have the 'edit_plugins' capability which is by default only granted to admins.
    2123
    2224If you're experiencing problems please report through support forum or check FAQ section. If you have suggestions feel free to submit your view.
     
    3032**ToDo:**
    3133
    32 * handling files in MU installations
     34* Adding Dashboard functionality ( and/or File View in Dashboard menu (WP_NETWORK_ADMIN) )
    3335* catching some not set requirements
    3436* adding in-code documentation
     
    3638
    3739== Changelog ==
     40
     41= 13.11.11 =
     42* rewrite based on the great [WordPress-Plugin-Boilerplate](https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate) of Tom McFarlin
     43* optimizations for Multisite installations
     44* securing Singlesite installations
    3845
    3946= 13.11.09 =
     
    8188== Frequently Asked Questions ==
    8289
     90= I am admin! Why can't i see the Tools > Log Viewer menu entry? =
     91If your on a Multisite installation you have to be a Super Admin.
     92If your on a Singlesite installation you additionally have to have the 'edit_plugins' role.
     93
     94= But i am a Super Admin with super powers and still can't see the Tools > Log Viewer menu entry! =
     95Pow! Slam! Donk! ... as stated you have to have 'edit_plugins' role. There are Wordpress constants like 'DISALLOW_FILE_EDIT' which deactivates this even for the greatest of the admins.
     96Have a look at [http://codex.wordpress.org/Roles_and_Capabilities](http://codex.wordpress.org/Roles_and_Capabilities) or do a websearch for 'wordpress.org DISALLOW_FILE_EDIT' the have a talk to your site maintainer.
     97
    8398= How to enable debug.log =
    8499Simply add `define( 'WP_DEBUG_LOG', true );` in your wp-config.php file.
     
    91106
    92107= In Files View i only get the error message "Could not load file." or "No files found." =
    93 It looks like there isn't a *.log file in WP_CONTENT_DIR. Wich could mean there are no errors. Yay!
     108It looks like there isn't a *.log file in WP_CONTENT_DIR. Which could mean there are no errors. Yay!
    94109If there are files, it could be that they are not readable ( check your permissions ) or it's a bug ... Booo!
    95110
  • log-viewer/readme.txt

    r801627 r802754  
    1919
    2020To activate Wordpress logging to file you have to set `define( 'WP_DEBUG_LOG', true );` in your wp-config.php file.
     21In Multisite installations you have to be Super Admin for using this plugin.
     22Additionally inn Singlesite installations you have to have the 'edit_plugins' capability which is by default only granted to admins.
    2123
    2224If you're experiencing problems please report through support forum or check FAQ section. If you have suggestions feel free to submit your view.
     
    3032**ToDo:**
    3133
    32 * handling files in MU installations
     34* Adding Dashboard functionality ( and/or File View in Dashboard menu (WP_NETWORK_ADMIN) )
    3335* catching some not set requirements
    3436* adding in-code documentation
     
    3638
    3739== Changelog ==
     40
     41= 13.11.11 =
     42* rewrite based on the great [WordPress-Plugin-Boilerplate](https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate) of Tom McFarlin
     43* optimizations for Multisite installations
     44* securing Singlesite installations
    3845
    3946= 13.11.09 =
     
    8188== Frequently Asked Questions ==
    8289
     90= I am admin! Why can't i see the Tools > Log Viewer menu entry? =
     91If your on a Multisite installation you have to be a Super Admin.
     92If your on a Singlesite installation you additionally have to have the 'edit_plugins' role.
     93
     94= But i am a Super Admin with super powers and still can't see the Tools > Log Viewer menu entry! =
     95Pow! Slam! Donk! ... as stated you have to have 'edit_plugins' role. There are Wordpress constants like 'DISALLOW_FILE_EDIT' which deactivates this even for the greatest of the admins.
     96Have a look at [http://codex.wordpress.org/Roles_and_Capabilities](http://codex.wordpress.org/Roles_and_Capabilities) or do a websearch for 'wordpress.org DISALLOW_FILE_EDIT' the have a talk to your site maintainer.
     97
    8398= How to enable debug.log =
    8499Simply add `define( 'WP_DEBUG_LOG', true );` in your wp-config.php file.
     
    91106
    92107= In Files View i only get the error message "Could not load file." or "No files found." =
    93 It looks like there isn't a *.log file in WP_CONTENT_DIR. Wich could mean there are no errors. Yay!
     108It looks like there isn't a *.log file in WP_CONTENT_DIR. Which could mean there are no errors. Yay!
    94109If there are files, it could be that they are not readable ( check your permissions ) or it's a bug ... Booo!
    95110
  • log-viewer/trunk/readme.txt

    r801627 r802754  
    66Requires at least: 3.4
    77Stable Tag: 13.11.09
    8 Latest Version: 13.11.09-1728
     8Latest Version: 13.11.11-2248
    99License: GPLv2 or later
    1010License URI: http://www.gnu.org/licenses/gpl-2.0.html
     
    1919
    2020To activate Wordpress logging to file you have to set `define( 'WP_DEBUG_LOG', true );` in your wp-config.php file.
     21In Multisite installations you have to be Super Admin for using this plugin.
     22Additionally inn Singlesite installations you have to have the 'edit_plugins' capability which is by default only granted to admins.
    2123
    2224If you're experiencing problems please report through support forum or check FAQ section. If you have suggestions feel free to submit your view.
     
    3032**ToDo:**
    3133
    32 * handling files in MU installations
     34* Adding Dashboard functionality ( and/or File View in Dashboard menu (WP_NETWORK_ADMIN) )
    3335* catching some not set requirements
    3436* adding in-code documentation
     
    3638
    3739== Changelog ==
     40
     41= 13.11.11 =
     42* rewrite based on the great [WordPress-Plugin-Boilerplate](https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate) of Tom McFarlin
     43* optimizations for Multisite installations
     44* securing Singlesite installations
    3845
    3946= 13.11.09 =
     
    8188== Frequently Asked Questions ==
    8289
     90= I am admin! Why can't i see the Tools > Log Viewer menu entry? =
     91If your on a Multisite installation you have to be a Super Admin.
     92If your on a Singlesite installation you additionally have to have the 'edit_plugins' role.
     93
     94= But i am a Super Admin with super powers and still can't see the Tools > Log Viewer menu entry! =
     95Pow! Slam! Donk! ... as stated you have to have 'edit_plugins' role. There are Wordpress constants like 'DISALLOW_FILE_EDIT' which deactivates this even for the greatest of the admins.
     96Have a look at [http://codex.wordpress.org/Roles_and_Capabilities](http://codex.wordpress.org/Roles_and_Capabilities) or do a websearch for 'wordpress.org DISALLOW_FILE_EDIT' the have a talk to your site maintainer.
     97
    8398= How to enable debug.log =
    8499Simply add `define( 'WP_DEBUG_LOG', true );` in your wp-config.php file.
     
    91106
    92107= In Files View i only get the error message "Could not load file." or "No files found." =
    93 It looks like there isn't a *.log file in WP_CONTENT_DIR. Wich could mean there are no errors. Yay!
     108It looks like there isn't a *.log file in WP_CONTENT_DIR. Which could mean there are no errors. Yay!
    94109If there are files, it could be that they are not readable ( check your permissions ) or it's a bug ... Booo!
    95110
Note: See TracChangeset for help on using the changeset viewer.