Search found 3870 matches

That sounds like a good plan overall.

they are definitely interrelated in my mind. If the Far Lanes section gets too big, we can break it into a basic info section to stay in Lanes and expand a Far Lanes page with all the details.
 

That sounds like a good plan overall.

they are definitely interrelated in my mind. If the Far Lanes section gets too big, we can break it into a basic info section to stay in Lanes and expand a Far Lanes page with all the details.

No concerns here.

Looks really good.

For the "Change username" question, I would just reword it to say you cannot change your username once it is selected. No need to keep the year reference any more.

I noticed that because the default typeface for Wazeopedia used a sans-serif typeface, the uppercase "i" looks like a vertical pipe or lower case "L". I see there were some hacks in some of the pages that used the  {{Key press}}  and tried to force a different typeface letter to ...

tenetienne wrote: ↑Wed Sep 07, 2022 3:33 am Updated the URL link at Dashboard. The rest of the page needs to be brought to current visuals though. Will work on that later tomorrow or later in the week. Didn't touch the other page yet.

 

Great. Thanks 
 

If anyone is interested, the current [[Dashboard]] page is out of sync with the current version of the active Waze page, now under https://www.waze.com/account.

Another Dashboard page is [[this one]].

Otherwise, I'll get to it when I am done with other updates in progress. 

ldriveskier wrote: ↑Tue Sep 06, 2022 6:29 pm The format is: https://www.waze.com/forum/memberlist.php?mode=viewprofile&un=ldriveskier
 

Thanks! Fixed.

I like this temporary solution link much better.
 

OK. I have a temporary fix to that noted problem. I was trying to find a way to have the PM link send users to a landing page where we explain the changes to private messages and then still give them the link to the target user, but I was unable to find a way to send a parameter to a non-template pa...

Thanks, Dave.

I'll do a quick visual fix to that and then continue working on a back end solution.