Recently in Chrome Dev Tools when I make local CSS changes, then refresh the page, the CSS changes stay. In the past, local CSS changes were not persisted, but the page would refresh to its original state as originally served from the server.
Is there a way to have Chrome Dev Tools behave as it used to, removing the custom CSS changes on page reload?
Related
I am doing this course on HTML, CSS, and Javascript for Web Developers on Coursera, as I am new to all this, and I have stumbled upon something that I think is very old information in the course, and not working anymore with the same tools as they have changed over time. So in this course we have the GitHub pages tool, which at that time could be used simply via the "deploy" button. Right now, the GitHub pages tool is disabled unless you create a branch, and it offers this GitHub Actions option under Build and Development, from where you can choose different workflows. By choosing any of them, you get the site deployed, but upon entering it, it gives 404 error. From my understanding, what's missing is the index.html file. How can you use the GitHub Actions tool to also have the index.html file and get rid of the error?
I have tried deploying from a branch, but I am missing valuable information on how to make that work.
I would like to generate a hyperlink to a read-only view of a specific revision of an Azure DevOps wiki page. The links provided on the Revisions page navigate to a commit review page with compare and preview tabs and include a Revert button (when permitted).
I have tried
https://dev.azure.com/[organization]/[project]/_wiki/wikis/[project].wiki?pagePath=%2Fpath%2Fto%2Fpage&version=[ETag] but the version is ignored and the latest revision is displayed.
https://dev.azure.com/[organization]/[project]/_wiki/wikis/[project].wiki?pagePath=%2Fpath%2Fto%2Fpage&version=[commithash] but the version is ignored and the latest revision is displayed.
https://dev.azure.com/[organization]/[project]/_wiki/wikis/[project].wiki?_a=compare&wikiVersion=GBwikiMaster&pagePath=%2Fpath%2Fto%2Fpage&version=[ETag]&view=preview which is viable but undesirable due to the risk of misguided reverts.
If you only set read-only permissions on Wiki security, the page you get using the third form of link has no Revert button, so there should be no risk of misguided reverts.
While I was editing README.md in one of my repositories, the process blocked somehow.
Since then, when I access that repository, status stays in 'Fetching latest commit… ' and I am not able to upload any files or edit them on the web.
The other repositories work. I do not have this repository on my computer (i have the files obviously), and the system does not allow me to clone it, not even delete it.
What can I do to regain access?
THOUGH DEFINITELY it does not the answer your question, but I want to post a solution for whom have the same problem but because of different reason.
For Forecomers having the issue
I had the same issue(just reached this question by googling), and I remembered disabling the javascript of my browser. Why don't you enable the javascript of your browser and refreshing the page? In my case the problem was solved after enabling javascript.
We are using ATG-Endeca Customer Store Reference integration 11.2. We have configured Preview and are able to see the changes reflected in the publishing store. However, the changes only get reflected after we Publish them using Experience Manager and not simply after saving. Is this expected behavior? Oracle states the following which seems like it is.
You need to configure your staging environment so that changes to Workbench content are automatically published to a generational store whenever the Workbench user saves them. The saved changes are immediately visible in Preview mode upon a successful publish.
I had same issue in my project, i solve this adding endecapreview layer in my ear.
See this doc: Experience Manager Save & Preview Button Does Not Show Unpublished Workspace Changes (Doc ID 2230799.1) in Oracle Support.
In Endeca 11.2 both the Preview/Authoring and live Web Apps use FileStores. When you save your configurations in the workbench only the Endeca Content Repository gets updated and not the FileStore used by the Preview/Authoring Web App. For that you have to publish the project (newly introduced in 11.2). To do this click the 'untitled work' link in your experience manager UI and click publish. This will write to the FileStore used by the Preview/Authoring Web App and the changes will be visible.
I'v pushed a new version of code to gh-pages for 5 hours but the page doesn't show the update when i use the Chrome on laptop. however when I check the page from Safari of my cellphone, it just show the updated Page.
what could possibly be the reason?
Probably a cache issue (GitHub page should set aggressive cache header)
Try and reload the page on Chrome without cache.
(Ctrl+F5 or Shift+F5)
(On Mac: Shift+Cmd+R)