Resolve data discrepancies between v2 and v3 of website
- or -
Post a project like this1604
£200(approx. $250)
- Posted:
- Proposals: 15
- Remote
- #2617381
- OPPORTUNITY
- Awarded
Top rated PHP Web Development | WordPress | Magento | Drupal | OpenCart | PrestaShop | Joomla
Leicester
♛ No. 1 ♛ UK's Professional Web Development , Web Designing, Magento , Shopify, WordPress , API Integration, Full-Stack Ruby on Rails Developer,Senior Front-End Developer (AngularJS / Node.js)
Chandigarh
Top Notch Laravel, WooCommerce, Shopify, WordPress | Mobile, Web & Software | js/jQuery, React, PHP | Linux Servers & Cloud Management | Scalable, Back-end & Front-end Developer & Designer
Tbilisi
Python | React| WordPress | Shopify | Laravel | Mongo Atlas | MySQL | Angular | AWS (Lambda, S3 Bucket, EC2, SES, DynamoDB) | React | Node JS | Banner Design | SEO | Digital Marketing
Kolkata
1015739373961050754117000512529661923742224445725495312775371284115129495373089002
Description
Experience Level: Expert
Estimated project duration: less than 1 week
We recently had to completely recreate a membership website from a relatively stable v2 to a new v3. We still have v2 accessible via a subdomain (inc FTP), v3 is now live. Full access can be given to v2 and v3 backends via our hosting platform.
As a result of this re-creation, all IDs for all entries in the WP databases changed. Various scripts have been created to pull over the v2 IDs in to the v3 world so that we can re-link all the entries - e.g. users, products, memberships, orders etc. - but it has caused a lot of data issues. The site uses Wordpress, with an Elementor framework, extensive use of the Advanced Custom Fields plugin, and WooCommerce with WooCommerce Memberships addon.
There are still several main areas that need detailed investigation and resolution, and are at a relatively systemic/back end/database level rather than a front end level. Known current examples (and therefore the scope of this project):
1) 3 (relatively lightly used) user forums are not showing on the front end on v3 but were on v2. The data needs to be moved over if it hasn't been already, and made live on v3
2) VAT has been incorrectly added on v3 for imported v2 orders that contain a membership product (which is VAT exempt). This needs to be removed to clean up the headline reporting figures shown for gross income
3) Users that changed their email addresses on from say a@a.com to b@b.com on v2 have had their user profiles set up as a@a.com (rather than b@b.com) on v3. This needs to be changed. We have a list of 5 known examples, but there are thousands of users on the site so a script is required to compare and update.
4) Add the ability for admin users to search the v3 WooCommerce orders by the v2 WooCommerce order IDs if this is possible
5) Any associated front end HTML/CSS required to reflect the end user output correctly given points above
As a result of this re-creation, all IDs for all entries in the WP databases changed. Various scripts have been created to pull over the v2 IDs in to the v3 world so that we can re-link all the entries - e.g. users, products, memberships, orders etc. - but it has caused a lot of data issues. The site uses Wordpress, with an Elementor framework, extensive use of the Advanced Custom Fields plugin, and WooCommerce with WooCommerce Memberships addon.
There are still several main areas that need detailed investigation and resolution, and are at a relatively systemic/back end/database level rather than a front end level. Known current examples (and therefore the scope of this project):
1) 3 (relatively lightly used) user forums are not showing on the front end on v3 but were on v2. The data needs to be moved over if it hasn't been already, and made live on v3
2) VAT has been incorrectly added on v3 for imported v2 orders that contain a membership product (which is VAT exempt). This needs to be removed to clean up the headline reporting figures shown for gross income
3) Users that changed their email addresses on from say a@a.com to b@b.com on v2 have had their user profiles set up as a@a.com (rather than b@b.com) on v3. This needs to be changed. We have a list of 5 known examples, but there are thousands of users on the site so a script is required to compare and update.
4) Add the ability for admin users to search the v3 WooCommerce orders by the v2 WooCommerce order IDs if this is possible
5) Any associated front end HTML/CSS required to reflect the end user output correctly given points above
Pete C.
100% (6)Projects Completed
7
Freelancers worked with
5
Projects awarded
54%
Last project
11 Dec 2023
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies