Again, as I wrote to you here on your talk page more than a year ago in my "Please hit the breaks" note – please do not be too hasty when it comes to finalizing official Wikispecies business. Ending a "Requests for Comment" matter only three days after it was issued is way too soon, especially when it comes to matters that might change the core functionalities of WS, such as imports. Many of our users log in perhaps once a week, and when it comes to important matters everyone should be able to have a say. That is also why our "requests for adminship votings" (or for bureaucrat dittos) are always open for at least seven days.
User talk:CreativeC38
Yes I taught about your message when I closed the RfC but it was too late, it was configured :/ I'll be more carreful next time
Thanks. Also, configuring stuff at Phabricator is not the same thing as closing the local RfC at Wikispecies, after all. If we want to discuss it again we now need to open up a new RfC here, which seems a bit odd only 80 hours after the first one was created. So if you're a bit less trigger-happy the next time, that will be appreciated. :)
You have the rights too import so could you import these pages ? And then I'll be able to setup translated templates. Thank you.
Sure thing, but there are a few other Wikispecies matters I've promised to take care of first – they were due yesterday... But I'll sort it out after that.
Hello again. Could you please take a look at Help talk:Translation? Thank you.
Done !
This post was hidden by CreativeC (history)
Hello. It seems I can't really get this translation business right... :-) Could you please check up on the Wikispecies:What Wikispecies is not page, and fix any irregularities or errors I might have added? Thanks in advance!
Of course :) I'll fix it soon
This page can be translate, but miss the translator header. Can you add it please?
done !
Hello Archi38. Please don't be so very hasty when archiving material, as you was here. There is absolutely no reason to archive material the very same day that the last message was added to the discussion. Please give the participants enough time to see the entire discussion: not all of our users log in every day. Regards, ~~~~
Sorry, I'm used to close RFC when it is finished (like on Wikipedia and Wikivoyage). Also with Flow you don't have to sign your message with 4 tildes.
The thing is that almost all processes are a lot slower on Wikispecies than in most of the other wikis – mainly because we have a much smaller base of active users (currently 199, in comparison to tens of thousands on enWP, for example).
As for the tildes: yup, I noticed. :-) Do the tildes thingy work at all in Flow? For example, in the traditional editing mode (without Flow) 5 tildes renders as a time and date stamp, but without the user name (or for that matter, 3 tildes renders as the user name only, without the date stamp.)
Tildes works (see try above). In flow you can switch between source and visual editors with the [[ ]] at the right corner of the edit section. You wrote your message with visual editor, so visual editor added nowiki balises at your tildes.
For the last message I used the source editor. Adding the piped link to the "Wikispecies active users" page was easy. However, when I tried to add a piped link to the equivalent page on enWP it added the "external link" symbol after the link, like this Active Users. Hence I switched to the visual editor, but then I couldn't create a piped link to at all, only an "un-piped" one. And not only for enWP, but for Wikispecies as well. If I add a pipe in visual mode, the "Insert" button in the "Insert link" window turns inactive (i.e. grey). That's not right, IMO.
Weird. I have no problem with Flow on frWP and Wikidata. Maybe just à lag ? But prefer the source editor for now.
The problem don't come from Flow. See in the village pump, i added a link to species (https) and it put the external link symbol too
That's because it is a normal web URL, starting with http/https. I'm speaking about true wiki links – I've changed your link in the Village Pump to a true wiki link, so you can spot the difference. Then it doesn't produce the external link symbol. But here in Flow it does: if I enter the exact same wiki code here as in the Village Pump, the external link symbol is added: Cross wiki notifications
Sorry, it turns out I changed the Village Pump wiki links added by User:Trizek (WMF) rather than by you. But still, the actual result is the same, as far as the external link symbol goes... :-)
I think @Trizek (WMF) could help us with this problem.
Perhaps, or rather: yes, hopefully. I'll leave him a note tomorrow.
Also, another issue: I saw your talk with User:Omondi regarding Flow. His edits are not auto-patrolled, so I thought I would mark his message to you as patrolled, while I was there. However that wasn't possible: instead I got an error message. That has never happened to me outside of Flow.
Try to purge your cache and restart your browser. This kind of message happens sometimes (really rarely for me).
Nope, no dice. Also, I use software that always and automatically clear the browser's cache, cookies etc every time I close the browser. I've tried Safari, Firefox, and Google Chrome: same result in all of them. The error message says "Session failure. There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again. Return to Main Page". This is not a very big deal since one can just as well use RTRC to mark pages as patrolled, but a bit annoying, never the less. I use a VPN service for my Internet connection, but never have had any problems like this earlier (probably partly because I'm a member of the "IP block exemption" user group.)
By the way, (temporarily) turning off the VPN service doesn't help, and the problem does not occur when patrolling other, "non-Flow" pages.
Weird. As I said, Trizek know more Flow than me, you so contact him
He is informed. (By the way, it turns out that using RTRC for patrolling Flow edits doesn't work either.)
There are no older topics