I've nailed it hehe :P

Is not that hard If one looks carefully to the Tabs table.... here's what I found ...

Imagine you have a page called "Contactos" (NOTE THE LINK MUST BE //Contactos too... I've noticed in my case the link was //Contacts) and this must be done right because my localized version (en-US) will be named "Contacts" and so the link is //Contacts... we can not ofc have two tabs with the same Path...

  So I inserted a new table in SQL most things are auto defined (unique keys)... now here comes the part were you can set any tab "to be" another tab localized version...

1st  - Set the culture code column to "en-US" since the original is pt-PT

2nd - Get the "UNIQUE ID" of the primary page.... in this case "Contactos" (pt-PT) this value will be the "DefaultLanguageGuid" in the localized version (en-US) "Contacts"

3rd - The LocalizedVersionGuid (last column) must be equal, so copy the ID from the original page!

Next I did a restart to my DNN application, I could see the new TAB in the EN-US version.... Cool :)

I guess I could also go to "Admin -> Pages" (in the en-US version) add a new pages and then go to SQL and change the values.... This is my next Test actually....

I hope my explanation wasn't much confusing... Perhaps it wouldn't be hard to make some "fix tool" for this but I'll leave that decision to you guys... I can do it in SQL, but others might end up with the same problem!

This is actually much more simpler than I thought, after spending sometime playing with this (in a live site... yeah crazy, but ofc I had backups)  

Anyway, its actually better to understand how this really works.... and the solution became very simpler, basically, we only need to set the "DefaultLanguageGuid" value to the original culture page "UniqueID" and that does it!  

So we can create a new page in the missing culture version...
Go to SQL (I used Management studio, because it makes it easy to copy paste the ID, but its not hard to make a query based on page name or ID)

Then you can restart your app, just to make sure everything is "refreshed" and go to the recent created page and "publish it" and copy module (or not etc) from the original...

Sebastian, perhaps its best to remove my previous confusing big post :P

Thanks

Yes I know, but thanks for the waring...

I do have such modules in this site, for example The Events module a great core module btw, its getting better and better... but in a site with localized content this kind of module becomes a problem, at least it did in the last few versions...

But I don't want to get off topic, in fact I have a thread about that specific module lost somewhere in the forum.

I've been messing around with Content Localization since the first I use DNN... Its still not enough but far better than before ;)