#3 — prettyPhoto.js does not adhere to prettyphoto_properties
by
Michael Zimmermann
—
last modified
Jul 20, 2011 07:42 AM
| State | Confirmed |
|---|---|
| Version: | 0.4.0 |
| Area | User interface |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Michael Zimmermann |
| Submitted on | May 07, 2011 |
| Responsible | Thomas Massmann |
| Target release: |
—
|
Using the following html code
<a class="prettyPhotoIframe" href="/path/to/image/folder/@@placegalleryview">Link Name</a>
gives me a plonetruegallery embeddded into a prettyphoto overlay which is shown above the site. This works well. Except one issue, namely:
For smaller screen sizes, the overlay area is not large enough. Changing portal_properties > prettyphoto_properties does not help as the code posted above uses prettyPhoto.js where the 75% values are hardcoded.
Solution:
Make prettyPhoto.js use the prettyphoto_properties as defined via zmi > portal_properties.
<a class="prettyPhotoIframe" href="/path/to/image/folder/@@placegalleryview">Link Name</a>
gives me a plonetruegallery embeddded into a prettyphoto overlay which is shown above the site. This works well. Except one issue, namely:
For smaller screen sizes, the overlay area is not large enough. Changing portal_properties > prettyphoto_properties does not help as the code posted above uses prettyPhoto.js where the 75% values are hardcoded.
Solution:
Make prettyPhoto.js use the prettyphoto_properties as defined via zmi > portal_properties.
Added by
Peter Mathis
on
Jul 13, 2011 02:50 PM
i think this is a known JS resource registry caveat:after every change in prettyphoto_properties you have to hit the "save" button in portal_javascripts registry because the properties are cached.
Added by
Thomas Massmann
on
Jul 20, 2011 07:42 AM
Will be added within the next minor release.
Issue state:
Unconfirmed
→
Confirmed
Responsible manager:
(UNASSIGNED)
→
tmassman
No responses can be added.
If you can, please log in before submitting a reaction.
