4.10

Author: Bugfish

.gitattributes

@@ -14,13 +14,42 @@
 *.lang text eol=lf
 *.txt text eol=lf
 *.md text eol=lf
-*.bat text eol=lf
+*.bat text eol=crlf
 *.sh text eol=lf
 *.bash text eol=lf
+*.pl text eol=lf
+*.py text eol=lf
+*.json text eol=lf
+*.xml text eol=lf
+*.yml text eol=lf
+*.yaml text eol=lf
 
 # Denote all files that are truly binary and should not be modified.
 *.ico binary
 *.png binary
 *.jpg binary
+*.jpeg binary
+*.gif binary
+*.bmp binary
+*.tiff binary
+*.tif binary
 *.odt binary
 *.odf binary
+*.pdf binary
+*.zip binary
+*.tar binary
+*.gz binary
+*.7z binary
+*.rar binary
+*.mp3 binary
+*.wav binary
+*.flac binary
+*.mp4 binary
+*.mov binary
+*.avi binary
+*.mkv binary
+*.exe binary
+*.dll binary
+*.woff binary
+*.woff2 binary
+*.eot binary

.github/CODE_OF_CONDUCT.md

@@ -1,17 +1,11 @@
 # 🤝 Code of Conduct  
 
-We’re on a mission to create groundbreaking solutions, pushing the boundaries of technology. By being here, you’re an integral part of that journey. 
+We’re focused on developing innovative solutions and advancing technology. By being part of this, you contribute to our progress.
 
-**Positive Guidelines:**
-- Be kind, empathetic, and respectful in all interactions.
-- Engage thoughtfully, offering constructive, solution-oriented feedback.
-- Foster an environment of collaboration, support, and mutual respect.
+Positive guidelines include being kind, empathetic, and respectful in all interactions. It is important to engage thoughtfully and offer constructive, solution-oriented feedback. Fostering an environment of collaboration, support, and mutual respect is essential.
 
-**Unacceptable Behavior:**
-- Harassment, hate speech, or offensive language.
-- Personal attacks, discrimination, or any form of bullying.
-- Sharing private or sensitive information without explicit consent.
+Unacceptable behaviors include harassment, hate speech, or offensive language. Personal attacks, discrimination, or any form of bullying are not tolerated. Sharing private or sensitive information without explicit consent is strictly prohibited.
 
-Let’s collaborate, inspire one another, and build something extraordinary together!
+Together, we can partner to achieve common goals by following guidelines designed to promote effective collaboration and positive teamwork.
 
 🐟 Bugfish

.github/CONTRIBUTING.md

@@ -2,18 +2,19 @@
 
 I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.
 
-## How to Contribute
+We primarily accept security fixes and critical patches to maintain project stability and coherence. Feature updates are not accepted to preserve our backend architecture and overall project integrity.
 
-1. Fork the repository to create your own copy.
-2. Create a new branch for your work (e.g., `feature/my-feature`).
-3. Make your changes and ensure they work as expected.
-4. Run tests to confirm everything is functioning correctly.
-5. Commit your changes with a clear, concise message.
-6. Push your branch to your forked repository.
-7. Submit a pull request with a detailed description of your changes.
-8. Reference any related issues or discussions in your pull request.
+Below is an example of how to contribute to this GitHub project. Please follow this guideline and all other contribution rules carefully; otherwise, your request may be denied.
 
-## Coding Style
+- Fork the repository to create your own copy.
+- Create a new branch for your changes (e.g., feature/my-feature).
+- Make your changes and verify everything works correctly.
+- Commit your changes with clear and concise messages.
+- Push your branch to your forked repository.
+- Open a pull request to the main repository’s main branch with a detailed description of your changes.
+- Reference any related issues or discussions in your pull request.
+
+To ensure your implementation is effective and maintainable by other developers, please follow the code quality guidelines outlined below.
 
 - Keep your code clean and well-organized.
 - Add comments to explain complex logic or functions.
@@ -23,8 +24,6 @@ I am excited that you're considering contributing to our project! Here are some
 - Avoid code duplication by reusing existing functions or modules.
 - Ensure your code is easily readable and maintainable by others.
 
-## Issues
-
 If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.
 
 🐟 Bugfish

.gitignore

@@ -1,10 +1,5 @@
 # This is just an internal File to ignore Files during git operations
 
-# Block a File
-# folder/file.php
-# Block a Folder
-# folder/
-
 # Ignore all htaccess & htpasswd Files
-# **/.htaccess*
-# **/.htpasswd*
+**/.htaccess*
+**/.htpasswd*

CHANGELOG.md

@@ -1,5 +1,5 @@
 # 📑 Changelog
 
-Refer to the `_changelogs` folder for detailed insights into the changes made across different versions. The changelogs are available in **HTML format** within this folder, providing a structured record of updates, modifications, and improvements over time. Additionally, **GitHub Releases** follow the same structure and also include these changelogs for easy reference.
+Refer to the _changelogs folder for detailed HTML changelogs tracking updates across versions. These changelogs are also included in GitHub Releases for easy access.
 
 🐟 Bugfish 

CONTRIBUTING.md

@@ -2,18 +2,19 @@
 
 I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.
 
-## How to Contribute
+We primarily accept security fixes and critical patches to maintain project stability and coherence. Feature updates are not accepted to preserve our backend architecture and overall project integrity.
 
-1. Fork the repository to create your own copy.
-2. Create a new branch for your work (e.g., `feature/my-feature`).
-3. Make your changes and ensure they work as expected.
-4. Run tests to confirm everything is functioning correctly.
-5. Commit your changes with a clear, concise message.
-6. Push your branch to your forked repository.
-7. Submit a pull request with a detailed description of your changes.
-8. Reference any related issues or discussions in your pull request.
+Below is an example of how to contribute to this GitHub project. Please follow this guideline and all other contribution rules carefully; otherwise, your request may be denied.
 
-## Coding Style
+- Fork the repository to create your own copy.
+- Create a new branch for your changes (e.g., feature/my-feature).
+- Make your changes and verify everything works correctly.
+- Commit your changes with clear and concise messages.
+- Push your branch to your forked repository.
+- Open a pull request to the main repository’s main branch with a detailed description of your changes.
+- Reference any related issues or discussions in your pull request.
+
+To ensure your implementation is effective and maintainable by other developers, please follow the code quality guidelines outlined below.
 
 - Keep your code clean and well-organized.
 - Add comments to explain complex logic or functions.
@@ -23,8 +24,6 @@ I am excited that you're considering contributing to our project! Here are some
 - Avoid code duplication by reusing existing functions or modules.
 - Ensure your code is easily readable and maintainable by others.
 
-## Issues
-
 If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.
 
 🐟 Bugfish

README.md

@@ -10,16 +10,16 @@
 
 The Bugfish Framework, meticulously designed for web developers, prioritizes security, flexibility, and performance. Its architecture streamlines development processes, enhancing efficiency and scalability, while a dedicated community provides support and resources for developers to maximize their projects' potential.
 
-![Cover](./_images/framework.jpg)
+![Cover](./_images/_banner/framework.jpg)
 
-### Requirements
+## ⚙️ Requirements
 
-#### PHP Version
+### 🐘 PHP Version
 
-- PHP 8.3/8.4 is recommended.
+- PHP 8.4 is recommended.
 - You can find specific requirements in the different documentation sections of our libraries.
 
-#### PHP Modules
+### 🐘 PHP Modules
 
 - **`mysqli`** – MySQL database connectivity using improved extension.
 - **`gd`** – Image processing and manipulation (e.g., thumbnails).
@@ -38,7 +38,10 @@ The Bugfish Framework, meticulously designed for web developers, prioritizes sec
 - **`json`** – Parses and encodes JSON data.
 - You can find specific requirements in the different documentation sections of our libraries.
 
-### PHP Functions
+
+## 📚 Framework
+
+### 🐘 PHP Functions
 Discover a collection of indispensable PHP functions crafted for seamless integration across various projects. Witness how these functions expedite and refine coding processes within web development. Comprehensive documentation for each function is provided below. To incorporate these functions seamlessly, include the PHP files within the designated _functions subfolder in the overarching _framework folder. This strategic approach optimizes coding efficiency and enhances web project performance.
 
 | Name             | Description                                               | License  |
@@ -48,13 +51,15 @@ Discover a collection of indispensable PHP functions crafted for seamless integr
 | ✅ x_cookiebanner.php | PHP code to display and manage cookie consent banners. | LGPL-2.1 |
 | ✅ x_curl.php       | PHP wrapper or helper functions for cURL HTTP requests. | LGPL-2.1 |
 | ✅ x_eventbox.php   | PHP component for displaying or managing event boxes/messages. | LGPL-2.1 |
+| ✅ x_folder.php   | PHP component for folder-related functionalities. | LGPL-2.1 |
 | ✅ x_library.php    | Collection of utility functions for general use in PHP.  | LGPL-2.1 |
 | ✅ x_rss.php        | PHP script to generate or parse RSS feeds.               | LGPL-2.1 |
 | ✅ x_search.php     | PHP functions for search implementation and indexing.    | LGPL-2.1 |
 | ✅ x_table.php      | PHP helper for generating or manipulating HTML tables.   | LGPL-2.1 |
+| ✅ x_thumbnail.php   | PHP component for thumbnail-related functionalities. | LGPL-2.1 |
 
-### PHP Classes
-These classes, located in /_framework/classes/x_*, are crucial for their functionality, efficiency, and thorough testing across various websites. They enhance development and save time. Note: Some classes require a database connection. They will install necessary tables automatically if configured correctly. Not all classes require MySQL; refer to the documentation for specific requirements. If MySQL is needed, provide a valid x_class_mysql object to the class.
+### 🐘 PHP Classes
+These classes, located in /_framework/classes/*, are crucial for their functionality, efficiency, and thorough testing across various websites. They enhance development and save time. Note: Some classes require a database connection. They will install necessary tables automatically if configured correctly. Not all classes require MySQL; refer to the documentation for specific requirements. If MySQL is needed, provide a valid x_class_mysql object to the class.
 
 | Name | Description | License |
 |------|-------------|---------|
@@ -75,7 +80,7 @@ These classes, located in /_framework/classes/x_*, are crucial for their functio
 | ✅ x_class_mail | Handles mail sending operations, with a subclass for sending operation items. This class depends on x_class_phpmailer. | LGPL-2.1 |
 | ✅ x_class_mail_template | Creates mail templates with substitutions and footer/header options, compatible with x_class_mail. This class makes it easier to quick prepare E-Mail Templates to build E-Mails - to send out to customers or others! | LGPL-2.1 |
 | ✅ x_class_mysql | Provides MySQL database handling capabilities, along with additional features. This is another flagship of this framework. Most classes here need an x_class_mysql object to run properly. This class serves a lot in security and Error-Readability. It can make work much easier and has a Database logging system to store errors in Statements which may occur and much, much more! | LGPL-2.1 |
-| ✅ x_class_phpmailer | Manages email sending operations within the framework. This class is not made by me "Bugfish". It's the PHPMailer Class you can find on: [Github](https://github.com/PHPMailer/PHPMailer) | LGPL-2.1 |
+| ✅ x_class_mail_phpmailer | Manages email sending operations within the framework. This class is not made by me "Bugfish". It's the PHPMailer Class you can find on: [Github](https://github.com/PHPMailer/PHPMailer) | LGPL-2.1 |
 | ✅ x_class_perm | Controls permissions for users, including single-item permission objects. You can control permissions with this and it is storage-saving. 1-n Relation. If you are in search of a permission system and you won't build one on your own, then you have found what you have searched for! | LGPL-2.1 |
 | ✅ x_class_referer | Logs visitor referrers. You have some configuration functions to control how referrers will be saved into the database. | LGPL-2.1 |
 | ✅ x_class_redis | Offers control over Redis functionality. With this class, you can cache content on a Redis server, which will make your website faster. This may come in handy if your website is serving mass on dynamically generated content, which does not change so fast. PHP Module REDIS is needed to run this class. | LGPL-2.1 |
@@ -85,14 +90,14 @@ These classes, located in /_framework/classes/x_*, are crucial for their functio
 | ✅ x_class_zip | Enables file compression and decompression, compatible with x_class_crypt for direct encryption and decryption. PHP Module ZIP is required to run this class. | LGPL-2.1 |
 | ✅ x_class_version | Fetch version information and information about the author at the currently deployed framework instance. | LGPL-2.1 |
 
-### CSS Classes
+### 🎨 CSS Classes
 Introducing the "Bugfish CSS Framework" – a solution for efficient web design. Simplify your development process with a comprehensive collection of pre-built classes, designed to expedite the creation of responsive web layouts. The Bugfish CSS Framework streamlines your design experience, making it faster and more professional. To use it, include the CSS files located in the css folder.
 
 | Name | Description | License |
 |------|-------------|---------|
 | ✅ xcss_xfpe.css | CSS framework with predefined classes for quick, simple styling. | LGPL-2.1 |
 
-### Javascript Functions
+### ⚛️ Javascript Functions
 Access a comprehensive array of JavaScript functions designed for integration across diverse projects, enhancing coding speed and efficiency in web development. Detailed documentation for each function is provided below. To incorporate these functions, include the JavaScript file in the _javascript subfolder within the central _framework folder. This implementation optimizes your coding process and elevates your web project's performance. Simplify your coding with our library of pre-built functions and modules, crafted to expedite the creation of dynamic, interactive web applications. Find the JavaScript Function file in: /_framework/javascript/*.js!
 
 | Name | Description | License |
@@ -116,15 +121,6 @@ If you encounter any issues or have questions while using this software, feel fr
 - **Discord Community** is available for live discussions, support, and connecting with other users: [Join us on Discord](https://discord.com/invite/xCj7AEMmye)  
 - **Email support** is recommended only for urgent security-related issues: [[email protected]](mailto:[email protected])
 
-## 📢 Spread the Word
-
-Help us grow by sharing this project with others! You can:  
-
-* **Tweet about it** – Share your thoughts on [Twitter/X](https://twitter.com) and link us!  
-* **Post on LinkedIn** – Let your professional network know about this project on [LinkedIn](https://www.linkedin.com).  
-* **Share on Reddit** – Talk about it in relevant subreddits like [r/programming](https://www.reddit.com/r/programming/) or [r/opensource](https://www.reddit.com/r/opensource/).  
-* **Tell Your Community** – Spread the word in Discord servers, Slack groups, and forums.  
-
 ## 📁 Repository Structure 
 
 This table provides an overview of key files and folders related to the repository. Click on the links to access each file for more detailed information. If certain folders are missing from the repository, they are irrelevant to this project.
@@ -149,6 +145,15 @@ This table provides an overview of key files and folders related to the reposito
 | [SECURITY.md](SECURITY.md) | How to handle security issues. |
 | [LICENSE.md](LICENSE.md) | License of this project. |
 
+## 📢 Spread the Word
+
+Help us grow by sharing this project with others! You can:  
+
+* **Tweet about it** – Share your thoughts on [Twitter/X](https://twitter.com) and link us!  
+* **Post on LinkedIn** – Let your professional network know about this project on [LinkedIn](https://www.linkedin.com).  
+* **Share on Reddit** – Talk about it in relevant subreddits like [r/programming](https://www.reddit.com/r/programming/) or [r/opensource](https://www.reddit.com/r/opensource/).  
+* **Tell Your Community** – Spread the word in Discord servers, Slack groups, and forums.  
+
 ## 📑 Changelog Information
 
 Refer to the `_changelogs` folder for detailed insights into the changes made across different versions. The changelogs are available in **HTML format** within this folder, providing a structured record of updates, modifications, and improvements over time. Additionally, **GitHub Releases** follow the same structure and also include these changelogs for easy reference.
@@ -157,18 +162,19 @@ Refer to the `_changelogs` folder for detailed insights into the changes made ac
 
 I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.
 
-**How to Contribute**
+We primarily accept security fixes and critical patches to maintain project stability and coherence. Feature updates are not accepted to preserve our backend architecture and overall project integrity.
 
-1. Fork the repository to create your own copy.
-2. Create a new branch for your work (e.g., `feature/my-feature`).
-3. Make your changes and ensure they work as expected.
-4. Run tests to confirm everything is functioning correctly.
-5. Commit your changes with a clear, concise message.
-6. Push your branch to your forked repository.
-7. Submit a pull request with a detailed description of your changes.
-8. Reference any related issues or discussions in your pull request.
+Below is an example of how to contribute to this GitHub project. Please follow this guideline and all other contribution rules carefully; otherwise, your request may be denied.
 
-**Coding Style**
+- Fork the repository to create your own copy.
+- Create a new branch for your changes (e.g., feature/my-feature).
+- Make your changes and verify everything works correctly.
+- Commit your changes with clear and concise messages.
+- Push your branch to your forked repository.
+- Open a pull request to the main repository’s main branch with a detailed description of your changes.
+- Reference any related issues or discussions in your pull request.
+
+To ensure your implementation is effective and maintainable by other developers, please follow the code quality guidelines outlined below.
 
 - Keep your code clean and well-organized.
 - Add comments to explain complex logic or functions.
@@ -178,6 +184,8 @@ I am excited that you're considering contributing to our project! Here are some
 - Avoid code duplication by reusing existing functions or modules.
 - Ensure your code is easily readable and maintainable by others.
 
+If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.
+
 ## 🤝 Community Guidelines
 
 We’re on a mission to create groundbreaking solutions, pushing the boundaries of technology. By being here, you’re an integral part of that journey.