Hi Blueshift

This sounds like an extension or a server module / glitch - I get the same if add a comment to the custom css file

Does anything show in the logs - have you checked with the host?

Do you have anything added in the htaccess? - looks like you might have
- try re-installing the default joomla htaccess

Cheers
Paul

    paulus1031 It already was (is) the default htaccess. Been 15 minutes since my last change...which should appear any minute now. Probably should just edit the source file at this point.

      I am a little outside my knowledge here but looking at the custom.css it has

      Expires: Thu, 28 Jun 2018 22:06:26 GMT

      Have you checked with the host / log?

      Cheers
      Paul

        paulus1031 Editing the less file directly, then compiling less to css produced....no change. This is strange. Going to try a different server.

          paulus1031 Changed the IP to a new devivce and location entirely. Still getting cache hits bringing up the site, though I cannot ping the site with a network tool. Something is very weird out there - not sure where the site is being cached, but I'm on the CloudFlare public DNS. Maybe I should see what Google DNS does.

            paulus1031 grid4wrap, like all the other grid rows, is set to .white-row but for some reason is coming up #000. This must have something to do with it being below main content, which is removed in this onepage treatment. Thoughts on how I can fix this?

            white-row.less was hardcoded to white-row {color: #0c2436;background: transparent;} which appears in dev tools.

            (edit: grid5wrap, too - so the rows below where main content would be)

              blue_shift Kindly confirm if managed to get along with solution for this or require assistance on the same 🙂

              If still further assistance required, Please provide screenshot marked with annotations as to how you wish to have the relative section seen so as to avoid confusion or ambiquity in addressing your query

                  aman204 This seems to be normal now - that's what my previous message meant. Unfortunately, we are divided by a common language. 🙂

                  Update to all: there were TTL issues in the eastern US yesterday pertaining to CloudFlare and Google Public DNS.

                      blue_shift Glad it is all sorted for you 🙂

                      Thanks for sharing the solution to relative issue which might help other members searching for somewhat similar solution pertaining to issue alike

                        Write a Reply...
                        You need to Login to view replies.