var Element fix for maps shuts off top right links

i am having a problem again. this time. the fix for the maps knocked out the

profile  account  logout

links on the top right. this has me stumped. here is the code that i still have yet gotten the links back with

--------------map controls work / links gone --------------------------------------------

 for (var Element in this.oBubbles)
            {
                sQueryParam = sQueryParam + Element + ':' + this.oBubbles[Element].count + ',';
            }

--------------map controls do not work/ links work--------------------------------------

 for (Element in this.oBubbles)
            {
                sQueryParam = sQueryParam + Element + ':' + this.oBubbles[Element].count + ',';
            }
------------------------------------------------------------------------------------------------------

the only change is to Element. declaring it as a var.

can anyone figure out how to get the

profile   accounts    logout

links back without turning off map controls?

it's probably something simple like a +3 or something.

Can you please post the offending file that doesn't work as an attachment. That way I or we can compare it with ours.

OK HERE IT IS. AS LISTEN UP ABOVE there is only one change to it.

the var element change

attached is file

I REMOVED THE VAR ELEMENT LOOP. BUT HAD TO RESTORE THE DATABASE TO AN EARLIER VERSION.

THIS SOLVED THE LINKS ON TOP RIGHT. AND PROBABLY A FEW OTHER THINGS.

WEIRD PART. IS IF YOU ARE A NON MEMBER YOU GET MAP CONTROLS (EVENTS)

TO MOVE AROUND ZOOM IN AND EVERYTHING ELSE. BUT

WHEN YOU LOG ON AS A MEMBER, THESE CONTROLS ARE NON EXISTANT.

THIS IS STOCK DOLPHIN 7.1.6.   I HAVEN'T BEEN ABLE TO FIX IT YET. ANYONE??

I assume you're using Dolphin 7.3.3

Thanks for sending the offending file. I really don't know what to say, but I compared it with the original file supplied with Dolphin 7.3.3 and they're not the same.

Your file has large chunks of code missing throughout and that's only the beginning. 

Have you modified this file of other reasons, or are you using a mod that's changed the file?

I would suggest that you isolate the offending file on the server by adding a couple of "--" in front of it

(-- extra_service_menu.html)

and copying the original Dolphin file to the Base directory. You may care to make the changes first, but don't recommend this. The aim is to get back to square one.

I'm inclined to think your other woes are part of this file corruption and by replacing the file they may go away.

Good luck.

Whoops. I just noticed you're using Dolphin 7.1.6. I completely missed that. Did you know, it's far more difficult to read sentences written in capitals. That is a proven fact. Plus CAPS on a forum is akin to shouting out loud.

1. Now I know why the files are different.

2. The hack probably does NOT (shouting) apply to your version of Dolphin, thus the errors.

3. It's very unwise to be using such an old version. Dolphin has been upgraded several times for obvious reasons.

4. You should be using 7.3.3 which contains very important security measures.

I doubt that anyone can help you whilst you're using such an old version of Dolphin. Come hell or high water, you should consider upgrading to 7.3.3 ASAP.

ergh. just tried updating. step by step from d7.1.6 to d7.3.3 and in all cases i got a

this is kinda making me crazy. not that i am not already. guess i am stuck with 7.1.6 at least most of it works.

Upgrading from one version to another has always been a pain for me. To jump several versions ???

I realise you probably have a large database, but a fresh install appeals to me.

Two things come to mind:

Are you running any mods or extensions? These probably won't work on the upgraded version and maybe they need to be dealt with first. However uninstalling some mods could delete important data in your database. Always backup your data first.

Secondly, look at this thread:

https://www.boonex.com/forums/topic/upgrade-from-7-1-6-to-7-2-2015-09-24.htm

It probably applies to your update attempt.

The most important thing here is to do all this on a duplicate site or backup your old site and go into maintenance mode. (preferred)