This is a good example for when it is good to "think outside the box", or in this case to look outside the box.
You don't want to know how long I spent looking inside #xRay, juggling things around, comparing with other similar items that still worked. #xRay worked previously and suddendly stopped after I did some cutting and pasting improvements. I knew I must have changed something, but what?
The blue highlighted "}" makes it clear.
I had cutout some css I no longer needed and failed to include the closing bracket in the cut which then caused #xRay to fail.
I'm sure glad my eyes finally strayed outside the #xRay box, or I'd been here all night letting this minor bug drive me crazy...;-)
That Blue Line sure makes it easy to see, doesn't it.
Next time I'll be sure to consider the surrounding area outside the box as a potential source of the bug.
My php.ini file generated an error log file in my hosting package
Note the backslash "\" at the front of the file name!
The backslash is a special character that made downloading and viewing the file with my terminal ftp difficult. I also could not delete the file. I also tried using my hosting package's "file manager" without success.
The phpErrors.log file is generated by the php.ini file. I edited the php.ini file to generate the error log file without the backslash and tested this. The new phpErrors.log file could be easily downloaded using ftp get command and deleted using ftp delete command. However the files with the backslash, e.g. "\phpErrors.php" remained. Then it hit me...
The backslash is a special character, so I should try escaping it! The escape character is also a backslash so I simply added an additional backslash to the file, e.g. "get \\phpErrors.log". Bingo! This worked!
I also tried: "delete \\phpErrors.log" which also worked!
I then deliberated editing my php.ini file to put the backslash back in front of the auto generated file. I could find no good reasons to do so with googleing the feature. So, I left it off. BTW, I found no useful info using google to resolve this problem. Glad I thought of trying to escape the special character. Hopefully this bug log will show up on google should anyone else find themselves wrestling with the same problem. I know, most of ya'll are smart enough to escape the special character in the first place. But then for some of us, "if you don't use it, you lose it...;-( But, all's well that ends well...;-)