Sarah_h Posted December 15, 2004 Posted December 15, 2004 .... For example, when I migrate to the production server and hand over to the client I'd like to remove options like "Use search engine safe URL's", and various non-essential options that I#d rather the client not muck about with? Sarah
♥Vger Posted December 15, 2004 Posted December 15, 2004 From a business point of view - bad move. e.g. Client mucks things up - has to come back to you, and pay you, to fix it again! (only joking - I think). To actually strip out all of the features you want to remove would be a bit of a nightmare - and there is no 'How To' to help you. Better way to do it would be to search for the text description for e.g. Use Search Engine Friendly URL's, and add after in brackets (do not alter). This way the client will know which items not to touch, it's a lot quicker, and if they ignore the advice and do it anyway then you are perfectly entitled to charge them for correcting their mistake. Vger
Sarah_h Posted December 15, 2004 Author Posted December 15, 2004 Vger, now that sounds like a plan!! Thanks, I'll give it a go. Sarah
Guest Posted December 15, 2004 Posted December 15, 2004 it could still come back to bite you in the ... . if the client comes to osCommerce and sees that functionality built in to the application, they may get a bit upset and then think you are 'putting osCommerce' together so they have to come back to you for changes, etc, it isnt worth the headache and pain. if the client mucks it up it is their fault, which is how i outline it, all details are there and if they change it, it costs them to fix it
ozcsys Posted December 15, 2004 Posted December 15, 2004 I must say I have a somewhat different view on removing uneeded things from the admin. A lot of clients want the interface as simple as possible so I do remove things that they will not need to mess with. This makes is easier for them to find the things that they need to find. Now I do explain this to them and if someone tells me that they want to see everything that is fine with me at which time I tell them that if they do break the store it is going to cost them to have me fix it. It is pretty simple to remove things from the boxes. Just go to the box and comment out what you do not want to show. I never delete anything just comment it out so it is easy to turn back on if needed. For the configuration box you need to go to your database and set them not to show there. It is the last field and anything you do not want to show you just change from 1 to 0. The Knowledge Base is a wonderful thing. Do you have a problem? Have you checked out Common Problems? There are many very useful osC Contributions Are you having trouble with a installed contribution? Have you checked out the support thread found Here BACKUP BACKUP BACKUP!!! You did backup, right??
longwave05 Posted April 27, 2006 Posted April 27, 2006 Hi there, you can remove sections from the admin panel by commenting out code in the column_left.php in the catalog/admin/includes folder.. eg. require(DIR_WS_BOXES . 'configuration.php'); require(DIR_WS_BOXES . 'catalog.php'); require(DIR_WS_BOXES . 'modules.php'); require(DIR_WS_BOXES . 'customers.php'); //require(DIR_WS_BOXES . 'taxes.php'); //require(DIR_WS_BOXES . 'localization.php'); require(DIR_WS_BOXES . 'reports.php'); require(DIR_WS_BOXES . 'tools.php'); This example hides the 'taxes' and 'localization' options in the Admin panel.
longwave05 Posted April 27, 2006 Posted April 27, 2006 You can also remove sub menus by commenting out specific lines in each of the 'boxes' files (catalog/admin/includes/boxes) around lines 23 to 33. This example removes three of the sub menu items from the 'tools' menu. if ($selected_box == 'tools') { $contents[] = array('text' => '<a href="' . tep_href_link(FILENAME_BACKUP) . '" class="menuBoxContentLink">' . BOX_TOOLS_BACKUP . '</a><br>' . //'<a href="' . tep_href_link(FILENAME_BANNER_MANAGER) . '" class="menuBoxContentLink">' . BOX_TOOLS_BANNER_MANAGER . '</a><br>' . //'<a href="' . tep_href_link(FILENAME_CACHE) . '" class="menuBoxContentLink">' . BOX_TOOLS_CACHE . '</a><br>' . //'<a href="' . tep_href_link(FILENAME_DEFINE_LANGUAGE) . '" class="menuBoxContentLink">' . BOX_TOOLS_DEFINE_LANGUAGE . '</a><br>' . }
Recommended Posts
Archived
This topic is now archived and is closed to further replies.