Superlinks Problem
Moderators: Developers, Moderators
Superlinks Problem
I am seeing an issue when I click on superlinks link in Firefox (like to google), the page loading will not display full screen. Please see the attached screen shot. It works great in IE. Cool plugin!
Thanks,
DEU
Thanks,
DEU
- Attachments
-
- SuperlinksProb.JPG (87.19 KiB) Viewed 14891 times
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Which version of Superlinks? and Firefox?
This worked for me last time I tried it (in Firefox)...
This worked for me last time I tried it (in Firefox)...
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
It appears that the code in the top_header.php is "causing" the problem. I haven't had much time to investigate, but my initial glace would be that the <TD> is limiting the size of the "rows to be used" or something along those lines (or the code is not being finished properly and that is causing the problem. Anyway, this only appears to happen with the console-based links (which depend on the top_header.php) versus the TAB'd links.
In superlinks.php, if you find the line:
and replace it with:
you won't get the "boxy" feel in the iframe, but it will "overlay" the console menu at the same time...not exactly a "perfect" fix.
also, something else that is strange. Although IE "appears" to work, if you re-size IE when the console link is selected (using the original code), the result is the same as the initial FF screen which leads me to believe IE is not interrupting the code properly initially either.
Anyway, attached are some screenshots
In superlinks.php, if you find the line:
Code: Select all
include_once("./include/top_header.php");
Code: Select all
include_once("./include/top_graph_header.php");
also, something else that is strange. Although IE "appears" to work, if you re-size IE when the console link is selected (using the original code), the result is the same as the initial FF screen which leads me to believe IE is not interrupting the code properly initially either.
Anyway, attached are some screenshots
- Attachments
-
- FF SS with the "boxy" feel
- superlinks-ss.JPG (76.44 KiB) Viewed 14824 times
-
- IE, initial link - no resizing done yet
- ie-unresized.JPG (91.57 KiB) Viewed 14824 times
-
- IE, resized
- ie-resized.JPG (80.81 KiB) Viewed 14824 times
I got the same problem with superlinks 0.8 and cacti 0.8.7g beta2.
I fixed that by adding following trick, just change
I fixed that by adding following trick, just change
toprint '<iframe src="' . $page['contentfile'] . '" width="100%" height="100%" frameborder="0"></iframe>';
in superlinks.phpprint '<iframe id="frame" src="' . $page['contentfile'] .'" width="100%" height="100%" frameborder="0"></iframe>';
print "<script type='text/javascript'>
function resizeIframe() {
var height=window.innerWidth;//Firefox
if (document.documentElement.clientHeight) {
height=document.documentElement.clientHeight;//IE
};
document.getElementById('frame').style.height=parseInt(height-document.getElementById('frame').offsetTop-72)+'px';
};
document.getElementById('frame').onload = resizeIframe;
window.onresize = resizeIframe;
</script>";
- TheWitness
- Developer
- Posts: 17007
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Howie was made aware of this over a month ago. I suspect that he is prepping a new version of Superlinks to deal with this. Like me, his is a very busy man.
Thanks for the patch!
TheWitness
Thanks for the patch!
TheWitness
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
This version of top_header from version E, I had to modified it to increase the size of the frame.
If you Use this with the latest version works well too.
LA
If you Use this with the latest version works well too.
LA
- Attachments
-
- top_header.php.txt
- (5.55 KiB) Downloaded 670 times
-
- Cacti User
- Posts: 367
- Joined: Tue Apr 05, 2005 9:52 am
- Location: Munich, Germany
Re: Superlinks Problem
i have tried all the workaround mentioned.. but none seems to work for me. i am still getting tabbed link in upper half of the page.
can someone tell me how to fix it???
using cacti 0.8.7g & superlinks 0.8
can someone tell me how to fix it???
using cacti 0.8.7g & superlinks 0.8
- TheWitness
- Developer
- Posts: 17007
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Re: Superlinks Problem
Attach a screen shot.
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Re: Superlinks Problem
Screen Shots are attached.
Behaviour is same in IE & Firefox. where as in Safari it shows a blank page in that area.
Behaviour is same in IE & Firefox. where as in Safari it shows a blank page in that area.
- Attachments
-
- In Safari Browser, Super links showing Blank Page i.
- Superlinks-Safari.JPG (29.07 KiB) Viewed 12039 times
-
- In Firefox Browser, Super link showing Page in Top frame.
- Superlinks-Firefox.JPG (43.25 KiB) Viewed 12039 times
-
- In Internte Explorer 8, Super link showing Page in Top frame
- Superlinks-IE.JPG (41.42 KiB) Viewed 12039 times
- mpdsville1
- Cacti User
- Posts: 71
- Joined: Wed Mar 16, 2005 12:11 pm
- Location: Albany , NY , USA
Re: Superlinks Problem
I'm still at an impasse with superlinks v0.8 on cacti version 0.8.7g as well ..
I've tried the two fixes listed in this thread and have found no joy.
I'm unsure how to try the css fix. exactly where does one place the style declaration?
Has anyone figured out exactly what is going on with this problem?
I've tried the two fixes listed in this thread and have found no joy.
I'm unsure how to try the css fix. exactly where does one place the style declaration?
Has anyone figured out exactly what is going on with this problem?
Who is online
Users browsing this forum: No registered users and 0 guests