All posts by undefined

Community Central

28,253Pages

Add new page

A reply to Absay

Absay·2d

Yes, changing the classification to something else (e.g. Data) does the trick but the infobox has to be removed from Cateogory:Infoboxes first. Otherwise, if the infobox is still included in the category, the classification change won't even stick.
I meant the infobox source editor. It has stuff many modern code editors have like auto tag closing, auto indentation, moving and copying lines with keyboard combos, line gutter with line numbers and collapsible scopes, warning/error/info counters, error handling, etc. It's really complete code-wise though not perfect. Hopefully they make it even better if they plan to change it.
Yep, I'm filing it as we speak, though I'm sure it's a very known issue.

Thanks again for your time.

A reply to Absay

Absay·2d

Oh, I see!

Thanks for the answer. Yes, just as I hit "Create post" it occurred to me to change the classification and test it from there, instead of having to learn the structure of the TD json object, which was my plan B but would have been a bit of hassle ;). Glad to know that workaround works.

Just curious, do you know if there are any plans to update the infobox template editor (and pray they don't take away any of its many useful editor features!)?

As for the bug report, does Fandom have a proper bug filing system? If not, I guess the zendesk report should suffice in this case anyway.

Absay·2d in Support Requests - Getting Technical

Does TemplateData work with Portable Infoboxes in UCP wikis?

I'm trying to add Templatedata to a portable infobox via the "Manage TemplateData" button in the source code editor, but upon hitting "Apply" the dialog just hangs and nothing happens. Clicking on "Cancel" does not work. I need to refresh the page but nothing is affected anyway.

TemplateData does seem to work fine with other non-infobox templates, as it applies the templatedata tag normally and the documentation is generated as it's expected.

For context:

PI: https://empireearth.fandom.com/es/wiki/Plantilla:Infobox_Edificio (TD is borken)

A regular template: https://empireearth.fandom.com/es/wiki/Plantilla:Icono (TD works)

Do portable infoboxes not get along with templatedata or am I missing something?

Infoboxes Templates

Absay·7/3/2016 in Support Requests - Getting Technical

[bug?] Adding links to labels in infoboxes propagates "ghost" links

Add a link to a label in an infobox, for example:

...
<data source="foo">
    <label>[[Foo]]</label>
</data>
<data source="bar">
    <label>[[Bar]]</label>
</data>
...

Now, suppose you put infobox in an article but leave out the "Foo" field because it's not needed in that specific article:

{{myInfobox
|bar = Some value
}}

When the infobox is rendered, it will only show the "Bar" field with its value and the label will link to [[Bar]], as it should.

But if you check Special:WhatLinksHere/Foo you still will notice the article with the infobox is listed there even though there is no actual [[Foo]] link anywhere on the page! The WhatLinksHere page is grabbing a "ghost" link and I strongly believe it's somehow getting it from the link added to the label regardless of it being rendered at all or not.

Is this supposed to be a bug or the normal behavior?

Thank you.

(edited by Absay)

A reply to Absay

Absay·1/16/2016

Yeah, I should have done that in my OP, sorry.

Here it is.

It all went down after the (+13). Every change upwards was me trying to undo the removals or trying to unsuccessfully roll back to the (+13) or getting only some pieces, but I managed to do a full roll back at the end.

At some point I got the Error message in my OP.

It's all normal now. It fixed itself, I suppose. But I'm not sure if it will happen again. I guess I should try.

(edited by Absay)

Absay·1/16/2016 in Support Requests - Getting Technical

Strange behavior when trying to submit CSS changes

There's something really weird happening right now.

I tried to add a few lines to a CSS page but when I submitted, it ended up REMOVING a massive amount of content from the CSS.

I tried to undo the changes but it removed a bunch of code again (twice!).

I tried again and got:

Error 503 Backend fetch failed
Backend fetch failed
Guru Meditation:
XID: 811197239
Varnish cache server

Also, the whole site seems to be abnormally slower than usual.

What's happening?

(edited by Absay)

A reply to Pinkgirl234

Absay·12/20/2015

Did you get it to work?

In case you didn't, try this:

.portable-infobox .pi-data-label div{
    background-color:#21CA27 !important;
}

(edited by Absay)

A reply to Nanococo

Absay·12/20/2015

I suggest you to read the basics first.

(edited by Absay)

A reply to Kevingr

Absay·12/9/2015

I'm sorry but the "This is a known bug, send feedback and we'll fix it" seemed just ridiculous to me. How can THAT be a bug?

If your first release is perfect, you've done something wrong.

Well, I never said the first release must be perfect. All I'm saying is that immediately assuming EVERY page in a wiki is a candidate for an infobox is as illogical as assuming every user should be given privileges to block people. This is unacceptable for perfect and imperfect first-time releases. It's like your first "well, except for..." case scenario when you are at the early stages of design.

(edited by Absay)

A reply to Absay

Absay·12/9/2015

How reviewing technical updates would solve anything? I mean, I would learn why they made bad decisions and when I can expect to see them in effect but I would still have problems nobody in the staff will be willing to even take into consideration.

(edited by Absay)

A reply to Kevingr

Absay·12/9/2015

Funny, I asked a similar question a few days ago (Thread:956672) and as you can see the only comments I got were "Tell the staff" and "Just ignore it". Yup. None of those answers were solutions to my problem.

This is truly outraging and baffling. How could Wikia "devs" not see that not all pages needed an infobox before they released the feature? What kind of development methodology were they following that allowed them to make such a stupid assumption? Because it looks really stupid when even Redirection pages are listed as "this may need an infobox".

(edited by Absay)

A reply to Absay

Absay·12/9/2015

The box is unchecked. FWIW I checked it and all it does is to remove any syntax highlighting whatsoever. I see now that I only get line numbers as long as "Infobox" is the template type, so the only workaround I can come up is to choose "Infobox", save the template, edit it to get the numbered lines, save it and choose another type.

And this is how Wikia hinders editing with stupid with not carefully planned features once again.

(edited by Absay)

Absay·12/9/2015 in Support Requests - Getting Technical

What happened to the numbered lines when editing a template in the source editor?

I tried to create a template using the source editor and I no longer get the numbered lines. Also, no automatic indentation either and no special syntax highlight, only the default for normal pages. They were really useful until the whole "Templates Types" nonsense was announced.

How can I enable those things back in my wiki? Thanks.

(edited by administrators)

A reply to Absay

Absay·12/7/2015

Yeah, they never respond and I'm not interested in sending feedback regarding a very illogical feature (assuming EVERY page may need an infobox tells you a lot about the design team).

Thanks for the answer anyway. JS will be then.

(edited by Absay)

Absay·12/7/2015 in Support Requests - Getting Technical

"Pages without an infobox" in Insights module is completely useless. How to disable it?

My wiki has 96 content pages and the module is telling me there are 184 pages without an infobx. The list is including redirections. Why on earth would I edit a redirection page?

How to disable that suggestion? Or if possible, deactivate the whole Insights module altogether. Thanks.

(edited by Absay)

A reply to Absay

Absay·11/22/2015

Thanks for the answer, that explains it. I guess the Variables paragraph on the Help page should be moved to the "On request" section below to avoid misleading information.

(edited by Absay)

Absay·11/22/2015 in Support Requests - Getting Technical

"Variables" extension is not working

It says in the Help:Extensions page that Variables is enabled by default, and it seems to work great here:

That 10 above is the result of using {{#vardefineecho:foo|10}}, but if I include that on any page in my wiki, it will come out as plain text, without the desired effect.

Should I need to do something else to get it to work in my wiki? Thanks in advance.

(edited by Absay)

A reply to Absay

Absay·11/6/2015

Yes, editing using external software shouldn't even be an immediate option for this, let alone the solution itself, but if that's the only way to go (for now), I have no major issues with it. For what is worth, I remember I looked for an external wiki editor at some point some years ago, so I guess this time I will have to switch.

Is there any good plug-in you recommend or does vanila Notepad++ include wiki markup support?

Thanks for the answer.

edit:

Alright, since I much prefer Sublime Text Editor for dev tasks, I found Mediawiker, which is a very nice package for live wiki editing, i.e. you work in the Sublime Text editor all the time, open and save pages, you don't need to copy from the ST editor and paste it to the browser. The drawback is that you don't have a preview button, obviously.

Unless you want to perform other tasks, such as protecting an article, this a great tool for straightforward editing. I recommend it to you over Notepad++. It's really easy to set up.

Thanks for leading me to this amazing tool!

(edited by Absay)

Absay·11/6/2015 in Support Requests - Getting Technical

Word wrap in source editor while in template mode

Every time I edit a template using the source editor I get the "new" one, with numbered lines and code auto-complete. This is a nice feature for infoboxes but for other templates the editor doesn't have a word wrap limit, so when lines get very long (e.g. writing text for documentations in template subpages), the editing experience becomes terribly inefficient and time-wasting. A workaround is simply manually adding new lines when the current is about to surpass the window but I really shouldn't being doing that nowadays.

Also, the auto-complete hinders editing for elements other than tags since, for instance, it creates additional apostrophes when I try to format with cursives or bold text.

Is there a way to enable word wrap for non-infobox template source editor? Alternatively, is it possible to selectively enable the new editor, so for example, I could disable it for template subpages?

Thanks for any help.

(edited by Absay)