In Chrome, I have a weird issue in the Media gadget. See the image below -- that dropdown is next to a file (on the right end of the row for a file). It's giving me "New Folder" and "Upload Files." This is wrong -- it should give me "Edit," "Cut," "Copy," etc.
This works in Internet Explorer. And it works for everyone else in Chrome. It's just my Chrome. The end result is that I have to switch to IE to edit media (because I have no way to get to that screen).
I have "Reset Views" (via My Settings in the interface).
I have forced a browser refresh (CTRL-F5).
I have disabled all Chrome extensions.
I have run CacheKiller and removed all client-side caching from Chrome.
Chrome is v38, which a release behind, but still only 3-4 months old.
Remember -- it can't be an EPiServer permissions, configuration, or server-side error, because it works for me (the same user, page, etc.) in IE. It simply has to be a client-side browser issue.
<p>To further confirm that it's just MY Chrome, I changed my password and had someone else login as me.</p>
<p>Works fine for them.</p>
<p>It is literally just <em>my</em> Chrome.</p>
<p>Reinstalling Chrome fixed it. It think it was a combination of have Chrome Canary installed and having my Google Updater broken. Correcting both fixed the problem.</p>
In Chrome, I have a weird issue in the Media gadget. See the image below -- that dropdown is next to a file (on the right end of the row for a file). It's giving me "New Folder" and "Upload Files." This is wrong -- it should give me "Edit," "Cut," "Copy," etc.
This works in Internet Explorer. And it works for everyone else in Chrome. It's just my Chrome. The end result is that I have to switch to IE to edit media (because I have no way to get to that screen).
I have "Reset Views" (via My Settings in the interface).
I have forced a browser refresh (CTRL-F5).
I have disabled all Chrome extensions.
I have run CacheKiller and removed all client-side caching from Chrome.
Chrome is v38, which a release behind, but still only 3-4 months old.
Remember -- it can't be an EPiServer permissions, configuration, or server-side error, because it works for me (the same user, page, etc.) in IE. It simply has to be a client-side browser issue.