Hi there! I see you're encountering a blank white screen when trying to add places on the desktop version of Wanderlog. I’d love to help you get this sorted out.

A blank white screen often suggests a loading issue or a problem with how the page content is rendering. To better assist, could you let me know:

- Which browser are you using with the WebKit rendering engine? (Is it Safari, or maybe a WebKit-based browser on Windows?)
- Have you tried refreshing the page or restarting the browser?
- Are you able to use other Wanderlog features without problems?
- Have you attempted clearing your browser cache or trying a different browser?

Meanwhile, here’s a step-by-step approach to fix this:

1. Refresh and Restart: Sometimes the page can get stuck loading, so try a simple refresh (Ctrl + R) or close and reopen your browser.

2. Clear Cache and Cookies: Cached data can create conflicts. To clear cache in most browsers:
- Go to the browser settings.
- Find Privacy or History settings.
- Clear browsing data, selecting "cached images and files" and "cookies."

3. Disable Browser Extensions: Some extensions can interfere. Try disabling extensions temporarily to see if that resolves the issue.

4. Try a Different Browser: If you're using a WebKit-based browser on Windows like Safari (which is rare) or a custom one, try Chrome, Firefox, or Edge to see if the problem reproduces.

5. Check Internet Connection: Make sure your internet is stable. A slow or interrupted connection can cause loading problems.

6. Sign Out and Back In: Logging out and back into your Wanderlog account can sometimes refresh permissions or sync issues.

If none of these steps work, there could be a temporary technical issue with the Wanderlog service. There have been reports on Reddit about some users experiencing white screens or pages not loading, which sometimes get resolved automatically on their side1.

Please give these a try and let me know your results. If you continue to have trouble, I can guide you to more advanced troubleshooting or escalate as needed.

Are you satisfied with the solution I provided so far?

it didnt work changin browsers from google to edge, and it isnt doing it on the app, only the website

Thanks for letting me know you've tried both Google Chrome and Microsoft Edge with the same issue, and that the app version is working fine. That’s helpful info!

Since switching browsers didn't help and the problem only happens on the website, it’s likely related to either your account session or perhaps some saved data like cookies, which could persist even across browsers.

Here’s what I suggest next:

1. Clear Cookies Specifically for Wanderlog: Sometimes cookies tied to your account or session can cause loading issues even if the cache is cleared. Go into your browser settings, find the cookies section, and remove any cookies related to wanderlog.com. Then reload the site and try adding places again.

2. Check Browser Console for Errors: Since you're on desktop Windows, you can open Developer Tools (press F12), go to the Console tab, and try to add a place. Do you see any error messages there? This can help pinpoint if scripts or resources are failing to load.

3. Try Signing Out and Back In: Though you may have done this, explicitly signing out from the web version, closing the browser, and signing back in can refresh your session data.

4. Disable Sync or VPNs: If you use any VPN or browser sync features, these sometimes interfere with session handling. Try disabling them temporarily.

5. Check for Network Issues or Firewall Restrictions: Some corporate or security firewalls block certain scripts or parts of websites, causing white screens. If possible, try from a different network or disable firewall momentarily.

Some users on Reddit have reported similar browser freezing and loading problems with Wanderlog on Chrome and Edge, but these tend to be intermittent and resolved by clearing data or refreshing the session1.

If these steps don’t solve your problem, I’m happy to help escalate this to technical support for deeper inspection or verify if there are any ongoing service-side issues.

Does that sound good? Let me know how it goes or what you find in the console! Are you satisfied with the guidance so far?