File "functions.js" is not included in the last package (b2 rev49).
Also I have other problems (they might be connected with this, since I use the functions.js from version 0.4.1?).
There is a hardcoded path "/assets/galleries/" in functions.js (when using slidebox) and it is not synchronized with "$path_to_galleries" from the snippet.
When I use slidebox embedded display, Gallery.xml is not created, there is no "xml_url" link in my code, there are no titles/descriptions in my gallery.
Lightboxv2 works a charm. Even if there are old gallery.xml files in the folder, no titles are showed with slidebox.
Where’s the catch?
I’m testing this on my dev site, so any dev code is also useful. Using Apache, FF2 and IE6.
Partially solved. It was a FF2 cache problem.
Quote from: andrazk at Dec 19, 2006, 06:05 AM
Partially solved. It was a FF2 cache problem.
Is there still some problems? There should not be functions.js file in v0.5.. and also not in 0.4.1..
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
I’ve got a problem with MaxiGallery installation. I did anything on install instructions, but:
1. When I insert [[MaxiGallery]] tag on page, nothing happens. I can’t see any buttons (i also logged in manager interface).
2. In manager interface when I go to Modules -> MaxiGallery, I see following message:
« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« `` is not numeric and may not be passed to makeUrl() »
Parser timing
MySQL: 0.0763 s (5 Requests)
I also don’t know what I might see here if everything is OK.
Quote from: timprox at Jan 03, 2007, 03:53 AM
2. In manager interface when I go to Modules -> MaxiGallery, I see following message:
MaxiGallery is a Snippet, not a Module.. Create it in the Snippets tab. Also, make sure that the document containing [[MaxiGallery]] snippet call is not cacheable (in the document page settings tab).
Quote from: andrazk at Jan 03, 2007, 04:03 AM
I was using MG 0.4.1 until now and I’ve switched to 0.5b2.
But somehow I cannot recreate the same thumbnails layout I had with <table>. Any advice, how to manage the <div>s to obtain the same effect?
I’d like to have N pics in a row, equally distributed, equally high and wide, centered vertically and horizontally.
Any help appreciated.
Can you give a link to the site? It should display the pics pretty much the same way it did before by default.. but I’m not a CSS expert and there is room for improvement there I’m sure. I did fix one layout bug that was reported (vertical centering of the thumbnails), but it’s in the SVN version. I will make a new beta release sometimes soon when I have done couple more feature requests..
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
I have succesfully included and configured MaxiGallery and a
Jquery autocomplete plugin for form inputs on test documents; but when I try to use them both on the same page, the 2nd one breaks.
This is a classic ’
addLoadEvent’ issue, i.e. the two script are both loading their own functions for the onLoad and the 1st one to get called gets overwritten by the 2nd.
Is there a known solution/workaround tested in MODx ?
Quote from: lukwe at Jan 04, 2007, 12:55 PM
I have succesfully included and configured MaxiGallery and a Jquery autocomplete plugin for form inputs on test documents; but when I try to use them both on the same page, the 2nd one breaks.
This is a classic ’addLoadEvent’ issue, i.e. the two script are both loading their own functions for the onLoad and the 1st one to get called gets overwritten by the 2nd.
Is there a known solution/workaround tested in MODx ?
I assume that this depends on the script you’re using to display the images (Lightbox, Slidebox, etc.). Check the JS that is included for those and see if you can just add your event to the end of the existing file (where it runs its onLoad). Or you could do what I often find works best: Just add your function call (for the autocomplete plugin) at the end of your HTML as normal JS (images won’t all have loaded at that point, but everything else should be ready by then).
I just tried this new version out last night, btw, and so far I’m really appreciating the templating and other changes. MaxiGallery just gets better and better. And with 0.95 scripts are properly registered and placed in the head also...
I have three quick and easy suggestions:
- Make the path to the snippet code a declared constant instead of hard-coding it. I have more than one MaxiGallery installation, and I like to develop the new stuff without affecting the old. That means that when I install into a new directory I have to edit all of those hard-coded paths.
- Add a variable to NOT register any scripts for the document head. I don’t like to use those (because I often tweak my includes), so I usually end up commenting out that function entirely and placing the include code in a gallery template. I’d prefer to just set a variable in the snippet call rather than having to modify the core files.
- How about adding a generic "Other" embed or slideshow type? I generally use Thickbox, which is not supported because jQuery and mooTools don’t play well together (but I love it for its modal versatility above and beyond image display). If I could choose an "Other" type and just set my templates the way I want them it would be easy for me (and anyone else) to use whatever crazy display script we happen to fancy.
Keep up the great work!
Just add your function call (for the autocomplete plugin) at the end of your HTML as normal JS (images won’t all have loaded at that point, but everything else should be ready by then).
This just disables MAxiGallery and loads Autocomplete... I just think pretending to use to different libraries on the same page is not the brightest idea... I’ll give up for now!
