Migration of the online store from Tilda to WordPress

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.

I am looking for a developer for a project consisting of 4 related tasks for the website best-matchmaking.com to be completed sequentially:Integration of a ready-made premium Blade template for blog articles + auto-generation of Schema/SEO markup (Article, FAQPage, Open Graph, canonical) for all current and future articlesRefinement of the blog structure: changing URLs with 301 redirects, renaming in the footer/menu/breadcrumbs, cleaning hidden code, removing categoriesNew block (photo + quote from a review) in the existing constructor for the main and landing pages = the ability to independently add text blocks between sectionsUnification of fonts, sizes, and colors across the entire site (except for the blog) — a single standard for headings and regular text, including header and footerDetailed technical specifications for each item — I am attaching them below via Google link.https://docs.google.com/document/d/1E5oQO2E-xmKJ3C0jW0ZsSPDBjaiELq0ETxfdivW6yIs/edit?tab=0 HTML samples and code will be sent in private messages after the response IMPORTANT! Please review all 4 tasks in detail before making an offer, especially the last one about fonts. There is quite a lot of work involved.Experience RequiredLaravel + Blade — confident, not beginner levelFrontend (CSS/JS) at the same level as backendExperience working with existing, not your own codeWork FormatBackup and test server before starting, transfer to production is MANDATORY — after agreement and testingMandatory self-check on all devices before submission — sending "ready, check" without your own testing is not acceptable. Bugs found after submission will be fixed within the same task. Bugs that arise during the transfer must also be fixed in production.Report with "before/after" screenshots for each itemDeadline and budget — after assessing the volume based on the detailed technical specifications. I look forward to your offers. Thank you

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

Currently, there is a store on OpenCart, and order emails are landing in spam. We need to ensure they go to Inbox (ukr.net gmail) and check it. The hosting provider wrote: Poor email delivery may be related to a low sender reputation - IP or domain. In this case, we can advise you to take the following steps to improve your sender reputation: 1. Switch the site to a dedicated IP address. When you use a shared hosting IP address with other users, your reputation may be harmed by the actions of other email senders. If one of the users sharing the same IP address sends spam or violates rules, it can affect the sender reputation for all users using that IP address, including you. Also, some email services limit the number of emails they accept from a single IP address, which can hinder the smooth operation of your email even if the overall reputation of the hosting's shared IP address is good. More details about ordering a dedicated IP address for hosting service: https://thehost.ua/hosting/ip 2. Check if SPF, DKIM, and DMARC records exist and are correctly configured on your domain. These authentication methods can significantly increase the likelihood of your email being delivered and are also mandatory for landing in "Inbox" on some email services. More details about the technical nuances of configuring these records can be found at: https://thehost.ua/wiki/email-reputation 3. Use the SMTP protocol for sending emails. 4. Use double opt-in for your mailing list. Do not launch email campaigns "blindly" - this increases the risk of landing in a spam trap for that email, which can lead to being blacklisted by spam filters for your IP or domain. 5. Avoid spam-like subject lines and stick to the context indicated in the subject line. Avoid trigger phrases, some of which are listed here: https://overloop.com/blog/455-email-spam-trigger-words-avoid-2018/