Jump to content

Alexandru

Clients
  • Joined

  • Last visited

  1. Strange part about this, is that was happening only in admin, and front-end was fully okay. I don't know, I didn't have the time to fully go into it. I mean on front-end you just edit custom.css and caches clear in css_built as far as I noticed, as in admin you can't do that, maybe would be helpful if you guys something to like resave css file for admin or / refresh. 🤔
  2. At first I fully focused on the server only, checked everything that could be related to caching and I had 0 caching on, not sure what happened here, but I glad I fixed this so I can move on, spent 4-6 hours per day in the last 48 hours and was a bit annoying. Anyhow, thank you for your time. Very much appreciated. 😇
  3. It looks like the issue was related to your software after all. After we deleted css_built_0, the system started generating the .css files again as expected. It might be a good idea to review the software behavior on your end before blaming the problem to the server. Anyway, final conclusion: it's a software bug related to caching or cache clearing. We didn’t dig too deep into it, but it’s definitely something you should look into. Why I say it's a software bug? Well I deleted all .cssfiles inside css_built_0 and the problem was still persistent, but after we deleted the entire folder, your software created it again and started creating the .css files inside the folder, then somehow IPS caches cleared ??? So, again, please review your software.
  4. We have Redis Enabled for caching, I checked that file "341e4a57816af3ba440d891ca87450ff_framework.css", I can see that on server is correct, no "www.domain" even though on web is cached, which is weird, we use Redis for caching, but even with that disabled still won't work. Interesting :)
  5. Cloudflare is DNS only, we don't use cloudflare as proxy. Can it be something saved in database to the old URL with www.domain for fontawesome ?
  6.    Alexandru reacted to a post in a topic: Blocked by CORS policy - cache issues
  7. I have updated access details and I also left some notes in there, thank you for the help. If you have any question you can PM me.
  8. Honestly, this points to be the software, changed back on www.domain in config and the CORS was now reversed, at this point doesn’t make any sense anymore, we checked our server in full top to bottom, nothing server-side. I honestly have no idea what is going on here. 🤔😶‍🌫️ What is strange is that is happening only in admin panel and on desktop, and after some research I found out that on mobile might work because of the way the browser handles www to non-www.
  9. matthew7ly started following Alexandru
  10.    Alexandru reacted to a post in a topic: Blocked by CORS policy - cache issues
  11. Okay, guess I have to figure this out myself. Thanks anyway, will post the solution here if I find it.
  12. I’m the host provider, and we don’t block anything. The question is, why are the fonts still loading from the old URL, even though we updated the URL in the config? What’s strange is that it’s working correctly on mobile. So…? Only the fonts (fontawesome) go with old URL from config www.domain and only in admincp, honestly doesn’t make any sense, I had this issue a few years ago, but I don’t remember how I fixed it 😂😅 Phone works 😂🤣
  13. Short terms, we switched to a new server and his config was with https://www.domain.com/ and I changed it to https://domain.com, now front-end has 0 issues, but back-end has that CORS Policy, from our tests we concluded that its related to cache, we tried multiple times clearing the cache, but didn't work.
  14. So we are getting this in /admin, tried everything by clearing caching and even changing caching methods, but still nothing. IDEAS ?!
  15.    Marc reacted to a post in a topic: Custom Fields Bug
  16.    Alexandru reacted to a post in a topic: Custom Fields Bug
  17.    Alexandru reacted to a post in a topic: Custom Fields Bug
  18.    Gary reacted to a post in a topic: Custom Fields Bug
  19. Found the problem. Not really the problem, but the solution so to say. I had to select "Yes, with full registration form" in order for me to get all settings on Customer Fields. Now we got these too. In case people will look for this in the future: System » Settings » Login & Registration » Registration and select second option from "Allow New Registrations?".
  20. What do you mean ? Both websites have the same settings.
  21. I’ve noticed that some customer fields are missing. I have two websites running the same version, but one of them displays more customer field information than the other. Version: 4.7.20 Website 1: Website 2: I I asked more people and 3 of them have Customer Fields exactly as in Website 2 Screenshot and 2 have it like Website Screenshot 1. What is going on here?
  22.    Matt reacted to a comment: Theme Hooks
  23. Alrighty then, my bad.