In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

View Revisions: Issue #990 All Revisions ] Back to Issue ]
Summary 0000990: Check that all configuration variables being used
Revision 2011-12-30 07:23:53 by alex
Additional Information Plan:
1. create a unix script to perform automatic check
2. export all configuration variable names into one file in one variable per line format
3. use that file as input for a unix command "find" command
4. this way "find" command will be called on all project files for each config variable separately and will output what's been found
5. there is surely a way to report only variables, that were not found at all

Idea is to automate process maximally.

Please inspect all modules.



Following configuration variables need to be implemented:
=========================================================
Category_ShowPick - show editor's pick categories above other categories when enabled
SocketBlockingMode - set socket blocking mode for all curl requests
Comm_City, Comm_Contacts_Additional, Comm_ZIP - show on all templates, where Comm_AddressLine1 configuration variable is used (e.g. orders_blocks.tpl in In-Commerce)


What is need to be done too:
============================
1. remember in order record (before user sends request to payment gateway; usually in ord:OnCompleteOrder event):
- currency (that was selected on front-end)
- totalamount of order in selected currency
Revision 2011-09-27 04:14:14 by alex
Additional Information Plan:
1. create a unix script to perform automatic check
2. export all configuration variable names into one file in one variable per line format
3. use that file as input for a unix command "find" command
4. this way "find" command will be called on all project files for each config variable separately and will output what's been found
5. there is surely a way to report only variables, that were not found at all

Idea is to automate process maximally.

Please inspect all modules.
Revision 2011-09-26 04:21:33 by alex
Additional Information Plan:
1. no need to check 1 by 1 all 326 variables. You can create large string from all configuration variable names and use some clever editor to search for them in PHP/TPL files and report ones that are not used anywhere.

Idea is to automate checking process.
Revision 2011-09-24 11:43:29 by alex
Additional Information



Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker