Thread

ok - let me get back to the client on this…

hmm. the client isn’t up to upgrading at this late stage right before they deploy. Is there another avenue we can travel to address this issue? This seems to be a weird config issue. If we can determine where/how the system is generating that specific variable, maybe it’ll help isolate the problem. Since the word “staging” isn’t in the database, it must be a config file somewhere. Any help would be greatly appreciated.

Update - Sorry I now see that you had typed it with a dash once and then with underscores the next time. I’m therefore guessing the first time was a mistake possibly?

I might be wrong on this but are you definitely seeing {meta-refresh} and not {meta_refresh} in the template?

I only ask as I was pretty sure that ExpressionEngine uses the latter version so I’m just wondering if that’s the case where your version with the dash in it has come from. Perhaps an extension? Custom System Messages perhaps?

Best wishes,

Mark

Indeed, a typo. We’re using the meta_refresh default variable

ok. found the issue. inexplicably, the previous developer hacked the core files and actually hard-coded a url for a refresh. ya.

Huh. Glad you were able to figure that out. Going to mark this as closed. Feel free to start a new thread if you have any more questions.