Всего: 872 Доступных коммитов |
Отфильтровано: 872 Коммиты |
Страница: 80 / 88
11.12.2025
Cleanup: Remove legacy config files and update README badges
Removed obsolete configuration files and templates:
- config/000config.php (legacy configuration)
- config/000config.php.bak (backup file)
- config/000config_global.php (legacy global config)
- config/000license.txt (legacy license file)
- config/changelog.php.example (moved to environment variables)
- config/lang.php.example (moved to environment variables)
Updated README.md:
- Split database badge into separate MariaDB and MySQL badges
- MariaDB: red badge for version 10+
- MySQL: purple badge for version 8.0+
- Improved visual clarity and readability
Impact:
- Cleaner configuration structure
- Removed redundant legacy files
- Better documentation presentation
Feature: Add Markdown formatting to Changelog module
Enhanced commit message display with basic Markdown support:
Changes:
- Added Markdown formatting for commit bodies
- Bold text: text renders as bold
- Lists: - item or * item renders as bullet points
- Inline code:
coderenders with gray background - Automatic line breaks with nl2br()
Technical details:
- Uses htmlspecialchars() with ENT_NOQUOTES
- Regex patterns for Markdown parsing
- Clean, simple implementation
- No external dependencies
Impact:
- Improved readability of commit messages
- Professional changelog display
- Better user experience
Location: admin/modules/changelog.php render() function
Add changelog.php.example template file
Security: Exclude secret configuration files from repository
Critical security improvement to prevent credential exposure in Git history: Changes:
Updated .gitignore to exclude files with secrets:
- /config/changelog.php (GitHub tokens)
- /config/lang.php (Yandex API keys)
- /config/config_lang.php (legacy API keys)
Removed secret files from Git index (kept locally):
- config/changelog.php
- config/lang.php
Created template files for developers:
- config/changelog.php.example
- config/lang.php.example
Security benefits:
- Secrets no longer tracked in Git
- Template files show required configuration structure
- Environment variables used for sensitive data
- Safe for public repositories
Setup instructions:
Copy .example files to actual config files:
- cp config/changelog.php.example config/changelog.php
- cp config/lang.php.example config/lang.php
Set environment variables:
- GITHUB_TOKEN: Your GitHub Personal Access Token
- YANDEX_TRANSLATE_KEY: Your Yandex.Translate API key
Note:
- Original config files remain on local system
- Only templates are committed to repository
- Secrets must be configured via environment variables
Impact:
- Enhanced repository security
- Prevents accidental secret exposure
- Follows industry best practices
- Compliant with GitHub secret scanning
Refactor: Optimize admin modules formatting and input validation
Enhanced three admin modules with SLAED coding standards and modern PHP practices: admin/modules/fields.php:
- String concatenation without spaces: 'text'.$var (SLAED standard)
- Opening brace on same line: function name(): type {
- Consistent single quotes throughout
- Improved code readability and maintainability
admin/modules/groups.php:
- String concatenation formatting aligned with SLAED standards
- All concatenations updated: removed spaces around . operator
- Consistent code style throughout module
- Better visual consistency
admin/modules/messages.php:
- Modern input validation with getVar() helper
- Replaced isset($_POST) with getVar('post', 'key', 'type')
- Added proper type validation for all user inputs
- String concatenation formatting updated
- Security improvements through proper input filtering
- Types: 'num', 'title', 'text', 'var' for different input types
config/changelog.php:
- Version history updated
README.md:
- Documentation improvements
Technical details:
- All string concatenations: 'text'.$var (no spaces)
- Function braces: function name(): type { (same line)
- Input validation: getVar() with proper type hints
- Security: Proper input filtering and validation
- Code style: Consistent SLAED standards applied
Impact:
- Improved code readability and maintainability
- Enhanced security through proper input validation
- Consistent code style across admin modules
- Better adherence to SLAED coding standards
10.12.2025
Refactor: Optimize fields.php admin module
Code optimizations applied:
- Remove unnecessary empty checks in foreach loops (2 places)
- Simplify complex condition in display logic
- Optimize input validation (combine getVar with ?: operator)
- Change validation type from 'title' to 'var' for better flexibility
- Improve code indentation consistency
Result: -8 lines, better readability, same functionality
Docs: Update README.md last updated date
Changed last updated date from January 2025 to December 2025
Docs: Fix README.md formatting for code block
Adjusted bash code block formatting in Installation section:
- Moved code block out of list item indentation for better rendering
- Improved markdown compatibility across different viewers
Docs: Comprehensive README.md optimization and modernization
Enhanced README.md with professional structure and detailed documentation: Content improvements:
- Added status badges (PHP version, license, status, migration progress)
- Added Quick Start section with 5-step installation guide
- Added detailed Installation section with 2 methods (manual + setup.php)
- Expanded System Requirements with PHP extensions
- Fixed typo: "Ngnix" → "Nginx"
Feature documentation:
- Categorized Features section (Core, Content Management, E-Commerce, SEO)
- Added detailed Project Structure with file descriptions
- Added Modernization Status section (50% complete, 2106+ SQL queries secured)
- Expanded Tech Stack with security details
Development guidelines:
- Enhanced Coding Standards with complete PHP code examples
- Added 8 mandatory function verbs (get, set, add, update, delete, is, check, filter)
- Added Security Best Practices with correct/incorrect examples
- Added Variable and Constant naming conventions
- Added Code Style examples with type declarations
Additional sections:
- Contributing Guidelines with Git workflow
- Expanded License section with GPL v3 details
- Support section with documentation/issues/forum links
- Professional formatting with emojis and clear structure
Technical improvements:
- Modern GitHub README best practices
- Better readability and scanability
- Comprehensive developer onboarding documentation
- Clear code examples for SLAED standards
Impact:
- Much more professional and comprehensive documentation
- Easier onboarding for new contributors
- Clear coding standards and security guidelines
- Better project presentation on GitHub
Cleanup and Configuration Update: Remove legacy files, untrack system configurations (.gitignore, .editorconfig), and fix changelog.