Wiki bugs/problems.

[Scaredgirl]

What happened was that spawn9859 did the Fire section, and I did the rest, which is why the Fire section looks a bit different. You can clearly see it in the upgraded card images that have more padding on them. It's not spawn9859's fault though. I didn't have time to explain the editing process, so he did it differently.

We need to do some copy-paste to fix the tables. Probably better to start fresh then to try to fix the current ones.

[akromat]

Does that mean that the original problem Lylle was posting about still exists?

[Scaredgirl]

Does that mean that the original problem Lylle was posting about still exists?

I don't know about that. To me the cards look good in Firefox and Chrome. It could be an issue with some other browser.

[Lyelle]

Tried all browsers today and the deplacement only occurs in firefox.
Im the only one with this problem?

[Scaredgirl]

Tried all browsers today and the deplacement only occurs in firefox.
Im the only one with this problem?

I went to recheck and yes, the problem definitely IS there. Darkness is almost perfect with only Pillar/Tower laid out incorrectly. Elements like Air on the other hand are total disasters with cards going all over the place.

[akromat]

Perhaps it has to do with the defined widths. A table as you know, always grows to fit the content so the overflow is probably pushing the tables to different widths.  It may be fixable with some css. Tougher to do since no css classes were set up in the table but still possible. That is, if that's even the problem.

I've compared obsidian pillar with liquid shadow and the code is the same. So it seems word-wrapping is what is shifting the table cell sizes.

[Scaredgirl]

Perhaps it has to do with the defined widths. A table as you know, always grows to fit the content so the overflow is probably pushing the tables to different widths.  It may be fixable with some css. Tougher to do since no css classes were set up in the table but still possible. That is, if that's even the problem.

Yeah, that's the #1 issue with the current system. Unfortunately I was in a dark place when I made the card table code (technical issues with the server) so I just pushed out the first crappy piece of code I could produce and I didn't care much about future problems.

We probably need to redo all the cards at some point using as much css as possible so we can do changes editing one file instead of 100+ files.

Anyone has experience in doing tables using only css? I haven't done that myself and I'm not even sure if it's wise.

I've compared obsidian pillar with liquid shadow and the code is the same. So it seems word-wrapping is what is shifting the table cell sizes.

Yep, it's definitely the word-wrapping that's the problem.

[Lyelle]

Perhaps it has to do with the defined widths. A table as you know, always grows to fit the content so the overflow is probably pushing the tables to different widths.  It may be fixable with some css. Tougher to do since no css classes were set up in the table but still possible. That is, if that's even the problem.

I've compared obsidian pillar with liquid shadow and the code is the same. So it seems word-wrapping is what is shifting the table cell sizes.

Its not a big deal converting the current code to css and would not solve the problem i think, because there's no failure in the current code.
Maybe div's solve the problem. ill take a look for a clean version.

[Lyelle]

pls try this:
go to your css an change the margin from 2em to 0.4em
p.table_rows{float:left;padding:0;margin:0 2em 0 0}

[akromat]

I didn't mean to change the code to pure css. I meant to add css to the existing code. Css changes could fix the problem because you can adjust the way table cells overflow and the way the browser breaks words for word wrapping.

As for making tables from pure css... talk about a nightmare. There are a few solutions but none are cross-browser compatible.

Even the simplest fix would probably require updating every single card page. If that's the case I would strongly suggest changing the way cards are added to the wiki. Maybe using forms instead of wysiwyg.

[miniwally]

When I double click sections to edit none of the bits that are already there come up so i can't edit it any solution to this problem I've tried on IE (where the edit section doesn't even come up after double click) and Chrome (where the already put in bits don't show).

EDIT: Please delete below post accidentally quoted instead of modified

[Scaredgirl]

pls try this:
go to your css an change the margin from 2em to 0.4em
p.table_rows{float:left;padding:0;margin:0 2em 0 0}

I'll put this at the bottom of my Wiki to-do-list. Fixing the card layout thing is important but there are 100 more important things to do first, like adding content and fixing bugs.

I didn't mean to change the code to pure css. I meant to add css to the existing code. Css changes could fix the problem because you can adjust the way table cells overflow and the way the browser breaks words for word wrapping.

As for making tables from pure css... talk about a nightmare. There are a few solutions but none are cross-browser compatible.

Even the simplest fix would probably require updating every single card page. If that's the case I would strongly suggest changing the way cards are added to the wiki. Maybe using forms instead of wysiwyg.

Yep. Might be best to go with what we have now. Later when the Wiki is "ready" and we are bored, we can redo the whole thing.

When I double click sections to edit none of the bits that are already there come up so i can't edit it any solution to this problem I've tried on IE (where the edit section doesn't even come up after double click) and Chrome (where the already put in bits don't show).

If you double-click and get a "-1", that means you don't have rights to edit that particular page. You see some of the pages are "pages" and some of them are "posts". Currently Contributors can only edit posts. It's a long story but I will explain it later and it will be changed at some point.

If you double-click a post and get "-1", you are simply not logged in. Click "dashboard" to do that.