Budget: 100 UAH Deadline: 1 day
Здравствуйте!
Есть большой опыт с WordPress.
Сделаю и покажу как сделал.
Обращайтесь!
===>
Есть сайт на вордпресс, как закрыть wp-admin, а вместо него сделать что-то вроде adminka.
wp-admin - при переходе чтобы выдавало ошибку допустим 404
adminka - работало как было wp-admin
Пробовал разные решение, но возникают проблемы с активацией некоторых плагинов. А бывало проблемы с активацией + еще wp-admin было без изменений и было 2 адреса wp-admin и adminka и работали 2 некорректно.
Пробовал плагины. Ситуация та же, некорректно работает.
Заплачу за правильный совет, если все будет работать корректно.
Budget: 100 UAH Deadline: 1 day
Здравствуйте!
Есть большой опыт с WordPress.
Сделаю и покажу как сделал.
Обращайтесь!
===>
Budget: 100 UAH Deadline: 1 day
https://uk.wordpress.org/plugins/better-wp-security/
перейти на вкладку: "Hide Login Area". установить флажок "Enable". в дополнительном поле вписать любое название.
Budget: 100 UAH Deadline: 1 day
Здравствуйте, закрою админку, и подскажу как самому делать, имею опыт разработки плагинов и сайтов Wordpress
Budget: 100 UAH Deadline: 1 day
Сделаю или подскажу как сделать. Есть опыт в закрытии админки
Budget: 100 UAH Deadline: 1 day
Напишите в ЛС - поясню. Напишите в ЛС - поясню. Напишите в ЛС - поясню.
Budget: 200 UAH Deadline: 1 day
Здравствуйте, Игорь!
Помогу сделать, делал в проекте вход в админку через адрес /vhodzdes
правильный совет, а не сделать проверку на существование get запроса по типу ?fjasdqeipkvj342ndfalkajf
если да то wp-admin если нет то 404
закройте через .htaccess и сделайте доступным только для своего IP адреса, как-то так
RewriteCond %{REQUEST_URI} ^(.*)?wp-login\.php(.*)$ [OR]
RewriteCond %{REQUEST_URI} ^(.*)?wp-admin$
RewriteCond %{REMOTE_ADDR} !^1\.1\.1\.1$
RewriteRule ^(.*)$ - [R=403,L]
а да, нужно добавить исключение для "admin-ajax.php", которое использует фронт для ajax запросов
RewriteCond %{REQUEST_URI} !wp-admin/admin-ajax\.php$
Самый рабочий вариант в .htaccess добавить
AuthUserFile .htpasswd
AuthName "Private access"
AuthType Basic
<FilesMatch "wp-login.php">
Require valid-user
</FilesMatch>
Файл генерируете сдесь http://www.htaccesstools.com/htpasswd-generator/ и кидаете в корень сайта
И еще вот это
<Files "wp-login.php">
Order deny,allow
Deny from All
Allow from ВАШ IP
</Files>
И живете сибе спокойно
After changing the PHP version from 7.0 to 7.4 on the OpenCart site, two elements have shifted slightly: the menu on the main page and the fields in the checkout process.
I want a bot for Telegram. Loading dialogues. With the help of AI, checking for potential lies. A website with advanced features. Registration, API, statistics, etc.
It is necessary to migrate the Opencart online store from PHP 7.4 to PHP 8.x. Currently, the core version is 3.0.3.8. We read that most likely the core will also need to be migrated to version 4.0 and there shouldn't be many difficulties... The functionality is mostly custom, and there are also Simple, OCFilter, Nova Poshta. We are waiting for recommendations and an approximate price. Ideally, someone who has already done similar work.
It is necessary to perform the update, transfer, and configuration of Laravel projects to a new server, ensuring stable operation, security, protection against exploits, and correct functioning of all services after migration. 1. Main tasks Prepare the new server for operation. Transfer project files, databases, configurations, and cron jobs. Update server software. Configure a secure environment for Laravel. Check compatibility of PHP, Laravel, Composer packages, and dependencies. Ensure protection against known exploits, malicious requests, and unauthorized access. Set up SSL certificates. Check the functionality of the websites after the transfer. 2. Transfer of Laravel projects For each project, it is necessary to: Transfer project files. Transfer the database. Transfer the .env configuration. Set directory access permissions: storage bootstrap/cache Check functionality: homepage; admin panel; authorization; forms; API; file uploads; email sending; cron jobs; queue workers.3. Security and protection It is necessary to implement basic and application-level protection: close root access via SSH; configure SSH access only via keys; change the default SSH port if necessary; configure the firewall; allow only necessary ports; install Fail2Ban; hide service versions of Nginx/Apache/PHP; restrict access to .env, .git, backup files, log files; set correct file permissions; check projects for malicious files; check Composer packages for known vulnerabilities; update dependencies if it does not break functionality; configure protection against SQL injection, XSS, CSRF, and path traversal; check the correctness of Laravel APP_ENV and APP_DEBUG; set APP_DEBUG=false in production; configure rate limiting for critical endpoints; check access to storage/uploads; configure protection against PHP execution in upload directories; check access rights to admin panels. 4. SSL and domains It is necessary to: Install SSL certificates. Configure automatic SSL renewal. Enable redirect from HTTP to HTTPS. Check the correct operation of websites via HTTPS. 5. Backup It is necessary to configure backup: project files; databases; .env files; uploaded media; cron configurations; Nginx/Apache configurations. Backup should be performed automatically on a schedule. It is preferable to store copies separately from the main server. 6. Post-transfer verification After migration, it is necessary to check: absence of 500/403/404 errors; absence of critical errors in Laravel logs. 9. Result of execution After the work is completed, there should be: Laravel projects successfully transferred to the new server; websites are functioning stably; SSL is configured; the server is protected with basic security settings; access to critical files is restricted; backup is configured; cron and queues are operational; the old server can be turned off after final verification.
Optimization of the website jdgreta.co.uk on Shopify. SEO audit attached to the project. Main tasks - - Fix all meta data - Complete the technical specifications for the programmer (since this project combines tasks for both the programmer and SEO, if you are not a company - you can use assistance) - Fix minor noticeable flaws - you can visit the pages and add your observations to the bid - this is more than welcome. - Fix reviews as they are duplicated in the cards (screenshots added) we use Judge.me plugin - Fix text color in some places, for example in filters for better readability - Update the Next template