Click here to edit contents of this page.
Click here to toggle editing of individual sections of the page (if possible). Watch headings for an "edit" link when available.
Append content without editing the whole page source.
Check out how this page has evolved in the past.
If you want to discuss contents of this page - this is the easiest way to do it.
View and manage file attachments for this page.
A few useful tools to manage this Site.
See pages that link to and include this page.
Change the name (also URL address, possibly the category) of the page.
View wiki source for this page without editing.
View/set parent page (used for creating breadcrumbs and structured layout).
Notify administrators if there is objectionable content in this page.
Something does not work as expected? Find out what you can do.
General Wikidot.com documentation and help section.
Wikidot.com Terms of Service - what you can, what you should not etc.
Wikidot.com Privacy Policy.
I'm rating this wish up Bryce… I think you should too =P
Ooh, good idea!
BMC Creative | RoaringApps | @brycecammo
+1
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
What about updateText="The text to show instead Updating tags" parameter for the button?
Piotr Gabryjeluk
visit my blog
Where you can avoid using CSS and still keep things just as customisable, definitely go for it IMO. Makes things more user-friendly for users.
It's easier to say "use the updateText parameter" than explaining a CSS alternative to someone that has never used a custom theme.
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
I would prefer ""The text to show instead of Updating tags" since it is grammatically correct :-)
Hmm, it would be good but wouldn't allow us to completely hide the popup & shader if we wanted to (as intended by the wish). But if it is significantly easier to implement the text option, I'd be happy with that.
BMC Creative | RoaringApps | @brycecammo
Actually, the more I think about it the better it seems. Go for it!
BMC Creative | RoaringApps | @brycecammo
Are progress_text and success_text will be enough descriptive or we should use other names? It's implemented, last and worst thing - naming which will stay with us forever :>
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
It's deployed - but not yet documented (so we can change attribute names).
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
What are the class names you used? I think your suggestions of progress_text and success_text are fine, although I'd prefer progress-text and success-text (hyphens instead of underscores) since it's easier to type and is more in line with other class and ID names in the base CSS.
Just to be clear, you are talking about CSS classes as stated in the original wish and not alternate text to display when setting tags, right?
Community Admin