New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Website docpad.org broken? #428
Comments
Oh, yeah. In your
The last |
Is OK on Chrome, not on Safari. |
Looking into it. Feel free to help out too - repo is here: https://github.com/bevry/docpad-documentation |
Oh, try refresh your cache. It could be that the old javascripts that hid and show the old webchat widget are still present for you. Clearing the cache should fix it. |
Like magic! What did you do? BTW, docpad? Way cool. |
So it would be this commit - docpad-archive/website@690b77e - which kills the webchat widget, but your cached javascript didn't update as it should have, so it was still behaving as if we still have the webchat widget there (which no longer exists in the html) - I'll do some changes now to make sure with each deployment we force update of the javascript and css cache. Btw, thanks! Also thanks for your feedback on the other issues too. Much appreciated :) |
Alrighty, bumping the website version will now wipe the cache, yay! docpad-archive/website@2a6fac9 Closing :) |
Got it, makes sense. For sure. I think this is just awesome. It is great for several Web sites related to projects on which I am working. You know what I am missing to get it perfect? Three things, none of which really is inside docpad, but worth mentioning:
So other than day and night on docpad, you got a dayjob? |
Sweet, thanks for the suggestions. Perhaps repost them on #415 to make sure they get the attention they deserve. Re dayjob, yep sure do - http://bevry.me/about |
Is something wrong with the docpad.org site? Most links for documentation go to the chat channel at http://webchat.freenode.net/?channels=docpad
Even if I click on Documentation->Overview or Documentation->Core->API it goes to the same place?
The text was updated successfully, but these errors were encountered: