Skip to content
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

ca not export tag cloud function in widget #990

Closed
anonymous-matomo-user opened this issue Sep 19, 2009 · 4 comments
Closed

ca not export tag cloud function in widget #990

anonymous-matomo-user opened this issue Sep 19, 2009 · 4 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously.
Milestone

Comments

@anonymous-matomo-user
Copy link

Hello,

When i ask to create the cloud tag widget, the embeded code purposed to export as a widget on our website stays to default form, he is not updated "on the fly" to cloud tag form ?!

<div id="widgetIframe"><iframe width="100%" height="350" src="http://piwik.org/demo/index.php?module=Widgetize&action=iframe&moduleToWidgetize=Referers&actionToWidgetize=getKeywords&idSite=1&period=week&date=19-08-2009&disableLink=1" scrolling="no" frameborder="0" marginheight="0" marginwidth="0"></iframe></div>

hum hum hum...

the link itself show the possibily to see cloud tag / export tools
but not when i use the div export function purposed by piwik...

Keywords: tag cloud

@robocoder
Copy link
Contributor

Dupes #90.

@anonymous-matomo-user
Copy link
Author

Pffffffffffffffffffffffffffffffffff, can not reopen :-( WTF ! :-(

They are 1 cosmetic bug (see below) and 1 feedback (your #90

For the cosmetic bug, 350 value does not permit to export coz the iframe is too small and mask all tooltips on the down of the widget, it is mandatory to use 380 as height to see tooltips...

@anonymous-matomo-user
Copy link
Author

sorry to disturbed u. it was the last report i do. adios.

@robocoder
Copy link
Contributor

At the moment, the cosmetic bug is a wontfix. 350 is hardcoded into plugins/Widgetize/templates/widgetize.js -- there's no property, per se, which can be queried at design time to obtain the widget's rendered, runtime height (which could vary depending on the text size and browser).

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

2 participants