Budget: 50 USD Deadline: 1 day
Здравствуйте. Обращайтесь.
Необходимо спарсить email адреса с 2500 разных сайтов. Дам список в личной переписке
Budget: 50 USD Deadline: 1 day
Здравствуйте. Обращайтесь.
Budget: 200 UAH Deadline: 2 days
Добрый день, готов сотрудничать.
E-mail: [email protected]
Скайп:Genchish
Budget: 200 UAH Deadline: 2 days
Здравствуйте, Я - менеджер группы молодых web-разработчиков, хочу предложить Вам наши услуги.
Перечень услуг:
-Создание/проектирование сайта(самописные либо CMS):
-Сайты визитки;
-Блоги;
-Лендинги;
-Интернет магазины;
-Самописные(на самых гибких и стабильных фреймворках).
-Верстка;
-Сопровождение сайта;
-Размещение / регистрация на хостинге;
-Внедрение и разработка баз данных;
-Консультация по продвижению , проектированию , администрированию;
-СЕО продвижение.
Особое внимание уделяется разработке парсеров и скриптов для разных предметных областей, начиная с парсингов магазинов и заканчивая гибкой выборкой с 6+ параметрами.
-Парсеры (JS+PHP+JQuery);
-Написание скриптов (JS,PHP).
Примеры работ находятся ниже.
http://bedevlya.com/uk/
http://optika-chelny.ru/
http://xn----gtbbubbqpbavln.xn--p1ai/
Контактные данные:
Skype - Arge0_0
ВК - http://vk.com/swarge
E-mail - [email protected]
Месторасположение:
г.Одесса
С уважением, Роман.
Budget: 100 UAH Deadline: 1 day
готов выполнить
Budget: 50 UAH Deadline: 1 day
Здравствуйте, готова выполнить задание, имеется опыт в данной сфере. Давайте обсудим нюансы и я приступлю к выполнению.
Budget: 200 UAH Deadline: 1 day
Готов выполнить, обращайтесь.
We are looking for a PHP Backend Developer to refine and clone gaming projects. In the first stage, it is necessary to complete the existing project and adapt it to the technical requirements. After successful implementation, a series of similar tasks and long-term cooperation is planned. Confident experience in PHP backend development and experience with gaming projects are required. When responding, please attach examples of completed projects and briefly describe your role. Payment for task completion is $100, the price for subsequent development from scratch is negotiable.
Greetings! I am looking for an experienced WordPress/WooCommerce developer for a small but urgent task. Problem: We are integrating Instagram Shop (Meta). When transitioning from the Instagram shop to the site cart, Meta passes product parameters in its own format: ?products=ID:quantity. Currently, WooCommerce ignores this parameter, and the cart opens empty. What needs to be done:It is necessary to implement a handler (hook on init or through a proper redirect) that will intercept parameters from Meta and convert them into the standard WooCommerce format for adding to the cart: ?add-to-cart=ID&quantity=X. Example logic:Link from Meta: https://treskare.com/cart-2/?products=18446%3A3Should transform/redirect to: https://treskare.com/cart-2/?add-to-cart=18446&quantity=3 There is a basic example of code from our specialist (I will provide it in private messages). It needs to be checked, adapted to our site's theme/plugins, and tested to ensure the cart is filled correctly and there are no conflicts with current user sessions or caching plugins. Requirements for the performer: Excellent knowledge of PHP, WordPress, WooCommerce API.Experience with customizing the WooCommerce cart (cart/checkout).Availability of reviews and successful projects on WordPress. Mandatory testing: The performer must conduct a functionality check of the code. The new setup should not disrupt the standard ordering process on the site. Directly adding products to the cart from the catalog, changing quantities in the cart itself, and proceeding to Checkout must work without errors. Security and code isolation: The code must check for the presence of the products parameter and the correctness of the product ID before executing the redirect to avoid causing Fatal errors or redirect loops for regular site visitors. Work on a test copy (Staging) or backup: Before uploading the code to the "live" site, the performer must demonstrate the script's functionality on a copy of the site OR make a backup of the file being modified. Conditions for acceptance of work and guarantees:Payment is made only after a full functionality check of the code on the site.The project is considered successfully completed only if:The link from Meta correctly adds the product to the cart.The standard functionality of the site is NOT disrupted (normal product addition, order processing, payment/shipping plugin functionality works without failures).If technical errors occur after the code implementation (Fatal error, conflicts with WooCommerce sessions, or order processing fails), the performer is obliged to resolve them within this project at no additional cost.
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.