Fredo-p wrote:Just to clarify, I didn't mean to combine the RC names. I meant to make the State/Territories column one cell. So, instead of having two 6. South Atlantic, you would have just one cell. But the rest would be their own row to allow the {{}} codes to fill in properly.

Fredo-p wrote:Speaking of trouble, I took a copy of the table code that Kent provided. I tried to make the two cells in the first column that are duplicates (6. South East) as a single cell using rowspan="2" and had some crazy @ss results. Almost got it right, but no good. So I gave up. lol

OK. I now understand what you were describing. You were intending to keep the two RCs in their own rows and two bigger cells in the OTHER columns.

Were you ignoring Territory 4 with the same issue for some reason, or were you just working to try to come up with a solution to fix it and apply to both territories?

Again the automated template code prevents doing what you described until I rebuild it based on input from the other RCs (if I can get any of them to ever respond).

Assuming none of them ever respond to the question ( ) I was originally thinking to make two columns anyway for the RC: Primary RC and Secondary RC. If we had two in the same column, it is less explanatory. I can make space for the 4th column and the coding would be 10x easier for the automation.

OK. I have completed the respin of most of the templates to simplify their use at the user level, modified the names to be more applicable, removed a few some unnecessary template layers, and completely automated the regional coordinator names. Now 100% of all the regions are controlled by the {{RC/Data}} content. It includes space for one or two regional coordinators per region. If anyone changes in the future, only the {{RC/Data}} page needs to be updated and every page will automatically get the new update.

If anyone wants to reference a regional coordinator on other pages, check the coding on any automated regional page like Northwest.

Forgot to mention I have RC1 and RC2 in the same cell without the horizontal rule line. It was easier to code this way, but if everyone thinks we really need the horizontal rule, I can likely whip up some code changes to include the rowspan when a second RC is present. I personally don't think it is necessary.

May I suggest that to keep only one place for all this data that I have this table built automatically from the current database I built? I can put comment text on the page for the necessary instructions. All the state template pages are driven from the database with this data. Otherwise the data will get out of sync.

kentsmith9 wrote:I don't know how many regional coordinators there are outside of the USA. Maybe someone can comment on that. If it is short enough, then we can put everyone on one table. I will set up the initial table with that field.

We have regional coordinators here in Australia (but we call them Regional Managers), same thing. We only have 5 RC's due to each editor responsible for their own State.

Let me know if you want those names for your list.

Can we migrate the map from the forum that holds that info for the US? I realize that makes the page US-centric, but that's the way it is for now anyway. As it builds, we can figure out if we need to migrate info out of it, reduce clutter, or whatnot, but the map was a great tool before the wiki page.

Thanks for doing this Fredo!

This is another example of why complex coding is moving from template language to Lua

Fredo-p wrote:

qwaletee wrote:This is another example of why complex coding is moving from template language to Lua

What the hell is Lua? Don't tell me it's another form of code

It is.

template language is most markup, with a few control structures and functions thrown in.

Lua is a full programming language, with some weird typing. But, you can't write a template in it. So you create a template that USES a Lua module.

The Lua programming language is not all that complicated, though the loose typing can get you in trouble.