-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: HMTL data from table is inherited on main PHP page #8
Comments
I've had an nginx error pop through (sonarr crashed) but it stayed inside the wrapper. just thought I'd add |
I don't know much web development, but could you use something like this? |
Do you have any idea how to fix this? Weird HTML tags in the raw log files are being interpreted in the DOM making the raw text show up as HTML. Pretty rare, but really bothersome. |
Fix applied, Currently in DEVELOP branch for testing |
1. Added: LIVE UPDATING! 2. Fixed rouge HTML inheritance which makes UI unusable. See: #8 3. Added new "FLEX" bootstrap layout. See: #58 4. Improved: Search function 5. Added: Growl notifications 6. Added: ability to adjust the time display refresh interval NOTE: PLEASE ensure you update your config file in /assets/config/. You can do this by renaming your old config file, coping the config.php.sample to config.php, and then edit the newly created config.php file with your values.
added with v3.1 |
BUG:
If one of the loggers contains certain HTML in their LOG - the main PHP wrapper will inherit that code making the parent PHP page display incorrectly. (see screenshot below)
Workaround:
Determine where the parent PHP page starts displaying incorrectly, and manually CLEAR the target offending LOG file. You DO NOT need to delete the log, just open the log file and delete it's contents.
NOTE: If this is a common occurrence with a specific logger, MOVE the offending logger's LOG path to the end of LOG path list in your index.php file, example:
IN example below, SONARR is making the PHP wrapper page display incorrectly.
Screenshot:
The text was updated successfully, but these errors were encountered: