Last modified: 2014-06-03 08:42:30 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T67730, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65730 - New statement not saving
New statement not saving
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
Wikidata (Other open bugs)
wmf-deployment
Macintosh Mac OS X 10.9
: Unprioritized normal (vote)
: ---
Assigned To: Wikidata bugs
aklapper-moreinfo
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-24 18:10 UTC by daniel.jarratt
Modified: 2014-06-03 08:42 UTC (History)
2 users (show)

See Also:
Web browser: Google Chrome
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Screenshot of the problem (33.32 KB, image/jpeg)
2014-05-24 18:10 UTC, daniel.jarratt
Details

Description daniel.jarratt 2014-05-24 18:10:46 UTC
Created attachment 15474 [details]
Screenshot of the problem

When entering a new statement, the "Saving..." text displays indefinitely and the new statement is not saved.

On https://www.wikidata.org/wiki/Q1585737, I entered the new statement "part of" "Black Hills". After clicking "save", the text "Saving..." appears and never disappears. I reloaded the page and my new statement had not saved. This occurred when I am logged in and logged out, in Chrome and Firefox.

I am able to edit other things, such as the description of the item underneath its name. Saving that text works just fine.
Comment 1 Lydia Pintscher 2014-05-26 10:31:17 UTC
We just tried to reproduce this on 3 different computers. All worked. Can you reproduce this on another item? Can you add and edit other statements?
Comment 2 daniel.jarratt 2014-06-03 05:03:30 UTC
Perhaps it was a problem with my computer, though why I can't say. After a couple of days, and after restarting my machine, I could not replicate the bug either. I'm sure it wasn't just a browser issue at the time I reported the bug because the process failed in both Chrome and Firefox and I restarted both browsers completely. Well, I guess it's a ghost in the machine.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links