Skip to content
This repository has been archived by the owner on Mar 8, 2021. It is now read-only.

Updating Weblink #420

Closed
digitalime opened this issue May 13, 2015 · 6 comments
Closed

Updating Weblink #420

digitalime opened this issue May 13, 2015 · 6 comments

Comments

@digitalime
Copy link
Contributor

Saving a weblink resource does not seem to update the actual value of the 'weblink' field in the database. It remains the same as the one given when the resource was originally created.

@Deesen
Copy link
Contributor

Deesen commented Feb 7, 2016

Cannot recreate that issue.

@digitalime
Copy link
Contributor Author

digitalime commented May 10, 2016

To recreate issue:

  1. Create Resource
  2. Save Resource
  3. Change Resource Type to Weblink
  4. Set Weblink value to http://foo.bar
  5. Save Weblink and preview
  6. Page redirects to http://foo.bar as expected
  7. Go back and edit weblink
  8. Change Weblink value to http://something.else
  9. Save weblink and preview

Expected Behaviour: redirects to http://something.else
Actual Behaviour: redirects to http://foo.bar

Tested on Chrome 50, FF 38, Safari 9.1.1. All with and without browser cache activated.
Modx 1.1RC2

@Deesen
Copy link
Contributor

Deesen commented May 10, 2016

Thanks for explaining. I tested it again and I´m 100% sure this is a browser cache-issue. FF for example is caching the destinations of 301/302-redirections, for some browser its harder to clean this cache. For FF I am using the addon "Empty cache button", just pressing STRG-F5 will not clean redirections-cache.

Before using the FF-addon I get redirected to http://foo.bar . Immediately after clearing cache I get redirected to http://something.else like "expected".

@bossloper
Copy link
Contributor

can be closed?

@digitalime
Copy link
Contributor Author

digitalime commented Dec 8, 2016 via email

@bossloper
Copy link
Contributor

@digitalime ... that's for you to do. 'close issue' or 'close and comment'

Deesen pushed a commit to Deesen/evolution that referenced this issue Jan 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants