VE does not display that note when you are copying. At least if it did that, it warns the user that there is some problem.
Jan 13 2020
Jan 1 2020
Nov 7 2019
Nov 1 2019
Looks good. I must admit I am only seeing one globe this time but it seems it can be scrolled left and right forever (well, I did about 5-10 of scrolls in before I got bored and clicked on Brisbane). Each time I got coords that looked plausible.
Oct 28 2019
Agreed. I don't think anyone will be saying "no no, my event's being held in the other australia". :-)
Actually I didn't pan. Rather the map that opened for me was quite wide and had the globe repeating 2 or 3 times. That is, there were multiple Australia's on screen. I clicked on a random Australia and then zoomed in. So the problem may be seen as either there should not be more than one globe shown or the longitude should be calculated down to the range -180 to 180.
Oct 23 2019
Thanks all, Kerry
Oct 21 2019
The template does indeed seem to be the trouble maker. I just had the same problem on [https://en.wikipedia.org/w/index.php?title=Kia_Ora,_Queensland&oldid=922291754 Kia Ora, Queensland] when I tried to cut-and-paste "It is located at 2754 Anderleigh Rd (26.02817°S 152.77676°E)." where the coords are produced by a template. Another test case for you.
Oct 20 2019
I probably should add that I was reporting relative to [https://en.wikipedia.org/w/index.php?title=Woodgate,_Queensland&oldid=922128021 this version of the articles]. I have subsequently edited it (but it doesn't seem to have altered the problem).
Aug 6 2019
May 15 2019
May 9 2019
That isn't any help to the VEFriendly template which is specifically there to assist VE-only people edit pages on which the VE is not routinely available but that they need to edit. For example, the State Library of Queensland are very involved with 1Lib1Ref contributing over 1000 edits in the past couple of years (world leaders in both years). They are gearing up for their 2019 1Lib1Ref (which starts 15 May ) and discovered to their horror that they could no long edit their [[WP:SLQ]] pages (which have the VEFriendly template). Nor does it help them talk to me on-wiki as their support person as my User Talk page also uses VEFriendly template.
Apr 1 2019
Eureka moment. I have experimented with my preferences. The problem seems to be
I tried using French Wikipedia and everything was fine.
Yes, it still occurs with safe mode.
Mar 29 2019
The Auto Capitaliation setting make makes no difference to the behaviour.
It occurs either way.
Mar 28 2019
Mar 5 2019
Feb 26 2019
How do you duplicate an event but with a different date? I have a number of monthly events to set up. It doesn't seem possible to use the same name (QWiki Club), despite being on different dates because of the way the event page is named. If I just copy and edit the copied event page, then there appears to be no way to set the display name to be different to the new event page name. It's OK if they are differently named event pages, but the display name on Future/Past events should be the same.
There will seems to be issues with the timezone and UTC fields. Surely UTC is determined by timezone, state and date and is not independent. At the moment, there is no error message in relation to UTC but the event does not display and gives error messages when trying to display the time (which don't explain what the problem is).
Dec 14 2018
It seems to be part of a broader problem with clicking to the left of the article "rectangle". Yesterday I was trying to paste text at the start of a paragraph and the the paste kept getting added to the start of the article. The extent of the area you can click to place your cursor at the start of a line requires the user to be super-precise. If you miss the area (which of course is not displayed online so pretty easy to get it wrong!), the focus goes north (start of article, start of section?).
Nov 29 2018
I thought it was fixed as I was having no problems for a while, but it struck again on [https://en.wikipedia.org/w/index.php?title=Queensland_Police_Service&type=revision&diff=871249590&oldid=871248597].
Nov 28 2018
And I probably should add that having one tab where I do nothing but repeated edits to the articles I am currently working on is my normal way of working. Because I start a lot of new articles, I get lots of problems with new page patrollers (or those with nothing better to do) causing edit conflicts so I tend to do lots of small edits to minimise the risk. As my way of working hasn't changed recently, this bug (irrespective of the cause) has been introduced due to some change in the past week or so. I could not have failed to notice it before. So look to changes in the past 1-2 weeks.
Yes, it could be the same. I use multiple tabs on my browser, one tab will always be the article I am working on, the others will be sources etc. So yes after each Publish Changes in VE, the next action I am very likely to make in that tab is to launch the VE on that same article. If this is correct, the problem would occur on every 2nd edit. I don't think it is that frequent. But I realise that lately I have mostly been creating new articles on Australian places which means construction a large infobox (Template:Infobox Australian place). As doing lots of template work isn't a particular strength in the VE, I often do those edits in source editor from the outset or switch mid-edit from VE to source. So that probably means I am not doing two successive VE-only edits as frequently as usual, so that might reduce the frequency of the bug to what I am experience (frequent but not 1 in 2).
Nov 26 2018
The problem persists. And I still cannot see any pattern to what is causing it. It does not appear to be a reaction to any specific editor action.
Nov 24 2018
I am editing Cornubia, Queensland on English Wikipedia. This is the [https://en.wikipedia.org/w/index.php?title=Cornubia,_Queensland&oldid=870451850 current version]. I added 3 templates at the top of the file (Use Australian English, Use DMY dates, more citations needed). Then I noticed that the Publish Changes was grey. Here is a screenshot. This article has not previously contained those templates. Yet look at my screenshot, you can see the 3 templates I have added. You can see the Publish Changes is greyed. However, I can undo the work I have done and redo it. I can do more edits. However, whatever I do, Publish Changes remains grey throughout all of this and clicking it does nothing.
The problem persists. I have learned that once it reaches the greyed state, it is not possible to undo (consistent I guess with thinking no changes have been made, despite changes being visible).
Nov 23 2018
Nov 15 2018
Oct 29 2018
Oct 18 2018
Sep 24 2018
May 7 2018
Hurray, it is working again!
Apr 17 2018
I note that we have 1Lib1Ref South starting May 15 so it's important that Visual Editor's citations are working OK with Trove citations since citation is the key element of the campaign.
Apr 16 2018
Mar 30 2018
Mar 21 2018
Mar 19 2018
Mar 15 2018
Mar 14 2018
I think the "unsaved changes hav been automatically recovered" feature makes it more important to have an obvious way to safely abort/cancel an edit. Previously there was no consequence to how you aborted/cancelled (and there are many ways to do it) but now there is. If you "exit" the wrong way, you created "unsaved changes" that will reappear later and cause unintended problems.
Mar 10 2018
When I train with the VE, it is a common question "how do I get out of this edit and start over".
Mar 9 2018
And I think the logs need to be examined to see if any other articles have been affected by the publishing of an aborted VE edits after other edits, as they will need to have the edits manually merged.
Mar 1 2018
It's funny that you should mention
Feb 28 2018
Having finally found out how to get back here - the notification I received did not provide any link back here.
Feb 27 2018
I see someone else reporting similar problems here:
Feb 23 2018
How about a button on the VE that takes a screenshot (or better still a Start/Stop recording) so you can see exactly what I can see. There are a lot of problems in the VE in execution (like the constant problem of how it repositions the text you are working on off screen) which cannot be demonstrated by a diff as it affects the user experience but cannot be captured either with a screen shot because the act of starting my tool to take a screenshot generally loses the popup on my VE screen. It also affects me in making training materials as there are some pop-ups/drop-downs that I just cannot screen capture.
Feb 22 2018
Feb 19 2018
Oct 27 2017
Yes. People are always telling me to do things in phabricator but I haven't been able to login to it. See this most [https://en.wikipedia.org/wiki/Wikipedia_talk:WikiLove#Strange_behaviour_by_WikiLove.3F recent example]. Everyone *says* it is automatic with my Wikipedia login and never listens to me when I say that it does not work for me because it works fine for them. But when you are sitting in front of the login screen and it takes you round in circles with different error messages at different times, there is NO help from that screen to troubleshoot it and no link to where you can ask for help. I have even been told to report the login problem on phabricator which is really useless advice when I can't login to it. Quiditty is the first person to take the trouble to find out why I can't login. So now I can, I'd like to report that there are lots of people like me who probably can't login and there is no way to get help to do so.
Oct 26 2017
At the very least, when you get the error message about the user name, tell the user that what they have to do is replace all the illegal characters with underscore to make it work (or at least that is what I was told and that worked for me).
Because WikiLove does not include any comment that it is a tool creates the problem that even not-so-users copy one manually and then break the syntax when they edit it to suit their purpose. So a comment would be a helpful way to get them to use the tool instead of trying to do it manually. It should include a pointer to the instructions to enable WikiLove (as it is a preference so it may not be enabled for all users).