From 02a1e9f1c48ecad479260f963f7eb6791aef1a3b Mon Sep 17 00:00:00 2001 From: Chuck Scott Date: Mon, 3 Nov 2014 15:16:31 -0500 Subject: [PATCH] Cleaned up some class and directory names for consistency --- controllers/{front_end.php => front.php} | 2 +- index.php | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) rename controllers/{front_end.php => front.php} (96%) diff --git a/controllers/front_end.php b/controllers/front.php similarity index 96% rename from controllers/front_end.php rename to controllers/front.php index b5a8a3c..e7a39b1 100644 --- a/controllers/front_end.php +++ b/controllers/front.php @@ -17,7 +17,7 @@ * This class controls which models are use for front-end functionality * of this plugin. */ -class glm_proto_front_end +class glmProtoFront { /** diff --git a/index.php b/index.php index a085b13..548b641 100644 --- a/index.php +++ b/index.php @@ -46,7 +46,7 @@ Directory and File Structure here. (See "Process Flow" below.) controllers Directory containing any controllers. Typically there - would be admin and front-end controllers in this directory. + would be admin and front controllers in this directory. css Directory containing any css files specific to this plugin. @@ -73,7 +73,7 @@ Directory and File Structure then there should be sub-directories for the various groupings of related view files. If using sub-directories, those should generally match the associated model directories. - It may also be wise to use separate front-end and admin + It may also be wise to use separate front and admin directories under views to keep things organized. @@ -179,8 +179,8 @@ if (is_admin()) { } else { - require_once(GLM_PROTO_PLUGIN_DIR.'/controllers/front_end.php'); - new glm_proto_front_end($wpdb); + require_once(GLM_PROTO_PLUGIN_DIR.'/controllers/front.php'); + new glmProtoFront($wpdb); } -- 2.17.1