Hey,
I am almost finishing my new store and going to push it to live in september after my vacations ends.
I already am running a wordpress website but it’s a pretty simple one, just company information, catalogues and a contact form.
I am kinda of afraid this time mostly becuase I never used woocommerce before and I am not sure how it will go. Will it for example be possible to test the store so I can see if the orders are working, if payments method work, how the receipts are made etc.
The other thing that worries me is how much I will have to do when it goes live. Because I imagine a lot of stuff involving links will be messed up, because anything that contains links is staging.website.com and when it goes live it will just be website.com. Basically there is a lot of stuff that I am leaving for when the website goes live to not mess it up and feeling kinda of overwhelmed.
Is there any tips to work this problem ?
I am also not a dev and theme support happens to end mid september so I am working on tight deadline in case some thecnical problem appears.
>anything that contains links is staging.website.com
i recommend developing and staging on website.com , i.e. the **exact** same domain as the real live website.
I’ve lost count of the number of ‘experienced’ devs who show a client a new site version on a different domain (devs.ownwebsite.com) , but still have loads of links **and media** pointing to the live website (website.com) – meaning that what they are demoing to the client is not ‘a new site’ – but actually a **mix** of new **and old** sites
ive been able to sit and watch the live site logs while dev is doing a ‘new site demo’ and watch their ‘new site’ pulling in all kinds of links and media and js from the live site. ugh.
I’ve also had to fight with some dimwits who were “100% sure that links to external service X arent working” because they were dev’ing (despite being told multiple times not to) on a sub-url from their own personal website, and the reason that X wasnt working, was that external service X needed to see ‘referrer’ matching the real proper live domain.
so… do a ‘hosts’ kludge. flush your browser caches. do your testing on the *real proper domain*. its worth the effort.