![]() What To Do After You Update Your WordPress ThemeĪfter your website has gone live with its new WordPress theme, don’t take it easy just yet!Įven though you’ve gone to great lengths to ensure everything is correct, it’s a good idea to keep tabs on a few things:Ĭompatibility across browsers is a major problem and isn’t something you should overlook. You can put them back in their original positions after switching. So before switching themes, take note of the widgets and their locations if you intend to keep them in the same location. These could be simple text, social media links, subscription forms, or advertisements. They can be placed in the sidebar or the footer and come in different forms to enhance your website. That being said, make sure to make a copy of every tracking code so that you can add it to your new site after changing your theme.įor WordPress websites, widgets are valuable resources. Otherwise, you won’t be able to monitor the effectiveness of your site after switching WordPress themes. If you’ve added analytics code to the current theme, it’s especially crucial that you follow this practice. Ignoring or overlooking these codes is among the most frequent errors that beginners make. ![]() There are also some WordPress themes that have a settings panel where you can add Analytics or Adverse code. Some users directly include their analytics tracking code in their theme files. Tracking codes help you monitor your web traffic. This will enable you to include them later in a WordPress plugin for your particular website or the functions.php file of your new theme. If you or your web developer made these changes, be sure to look through the theme’s files and make a note of all the extra code you’ve added in the past. People typically forget about these modifications because they were made only once. WordPress users who aren’t beginners anymore prefer to add code snippets directly to their theme’s functions.php file in order to customize their website. Copy snippets from the theme you’re using Thankfully, a lot of the best web hosting services allow you to install a WordPress backup plugin that will enable you to back up your entire website with ease.Ģ. This is the most crucial step to prevent any data loss in case you encounter problems in the process. (This is not an ad, I’m just shouting this out as a very cool tool.) With Inspect, I can plug in my real iOS device via USB and get a Chrome DevTools instance for it.Ways to secure yourself and your business online.ĭive into the world of selling online - successfully!īacking up your website allows you to restore your website when something goes wrong.Ī backup refers to making a copy of all of your blog posts, plugins, files, and database information. I didn’t think this was really possible, but then I saw Inspect. No Mac and still need to test on a real device? I just did a little testing and I found the Chrome DevTools a little janky to use (a giant left panel renders, the click-to-select element feature didn’t work, and I kept losing WebSocket connection). They even jack Chrome DevTools in there somehow. You can use something like CrossBrowserTesting to do this right on the web. ![]() ![]() But that’s - uhhhh - not super practical. I have heard of people running over to Best Buy or an Apple Store to quick debug something on a display machine. Select the real device (which must have Safari open on some website) and you’ll get a DevTools instance of that website. You have to have the phone plugged in via USB (no wireless charging connection or whatever) and then you’ll see the device in that same Develop menu. If you have a Mac, doing this is pretty similar to what we just did. And if you can run the iOS simulator, that means you can run desktop Safari as well, and thus even have access to DevTools that can reach into the simulator. I happen to have a Mac, so I can have XCode installed and thus have an iOS simulator that is pretty easy to pop open. Problem not showing here? Then the problem is actually unique to iOS Safari. Now you’re actually using Safari, which is way closer to iOS Safari than desktop Chrome is. Does it seem actually specific to Safari? Lemme check Desktop Safari first since that’s just a few clicks away. Note that this does a smidge more than just display your site in a smaller area: it sends the correct User Agent String and Client Hints for that device. Lemme just use the device mode in Chrome quick. ![]() These are my general steps, starting with not even using iOS Safari. ![]()
0 Comments
Leave a Reply. |