Quote from: spoetnik at Aug 18, 2006, 09:34 AM
mm, close but no sigar.
Using the above fix, shows the pictures verry nice, but i Dont see a "next" or "previous" button. Looks like the slidebox does’nt know where to find these picture-buttons i guess??
hmm, good point! Could you try to test the following; edit functions.php and..
change line 421 from:
$slidebox_script_str = "<script type=\"text/javascript\">var xml_url = 'assets/galleries/".$modx->documentIdentifier."/gallery.xml';</script>";
to:
$slidebox_script_str = "<script type=\"text/javascript\">var xml_url = '" . $modx->config['site_url'] . "assets/galleries/".$modx->documentIdentifier."/gallery.xml';</script>";
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
Thanks verry much for the quick reply. You are my hero of the day, this works!!
Just one little hickup, it doesn’t show the little ’X’ to close the slideshow. I dont know how to fix this.
Maybe this would be a sollution for a future release.
Thanks verry much, the community makes MODx even better!!
How about a Thickbox (
http://jquery.com/demo/thickbox/) version? I have created my own, but since I first stripped out all the other stuff I didn’t need and added a lot of weird code specific to the site I’m working on now (two more image sizes, etc.) it’s probably not in a useful state for others. I like Slidebox, but the XML files get cached by users’ browsers and so it wasn’t updating consistently (plus the Slidebox JavaScript is way too sophisticated for me; I just wanted to add a dynamic link to the bottom of the display window and it damn near killed me).
I could take a look at the thickbox probably.. I know that many users are already using it in maxigallery..
Quote from: metrotype at Sep 18, 2006, 02:29 PM
You cannot put a <b> or </b> or </br> inside an an attribute.
Yeah, my bad.. that is just there to make the picture descriptions look pretty in lightbox v2..
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
Doze, is there a reason to use your own scriptaculous and prototype version, there are inside the MODx release and the size of file increase a lot. Why don’t use the script in "manager\media\script\scriptaculous\scriptaculous.js" ?
I think a script management will be a good thing a kind of :
if (!$modx->isloaded_script(’scriptaculous’) include(’script’)
No reason I guess.. I think at somepoint lightbox or slidebox needed specific version of prototype / scriptaculous..
I’ll change it to use the ones that are in modx. There’s no need to do "script management" at the snippet side, modx api regclient** functions does that automatically.
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
Hi, I am very new to modx and am trying to setup the maxigallery. I have read alot of the posts in here and i am not sure if my problem is that my server is in safe mode? or that i am needing to patch my doc.parser file? or something else completely?
firstly i have installed everything as per instructions, (and have maxigallery running fine on another server) but when i add a standard call:
[[MaxiGallery? &display=`embedded` &embedtype=`lightboxv2` &pics_in_a_row=`3` &max_thumb_size=`110` &max_pic_size=`0` &thumb_use_dropshadow=`1`]]
the page doesn’t load and i get the following error (sorry i am a bit of a newbie and my debugging is fairly bad).
trlen($validParents)-1); $tblContent= $tbl = $modx->getFullTableName(’site_content’); $activeClause= $showPublishedOnly? ’AND published = 1’: ’’; $query= "SELECT id, pagetitle, longtitle, description, introtext FROM $tblContent WHERE parent IN ($validParents) $activeClause ORDER BY $sortby $sortdir"; if (!$rs= $modx->db->query($query)) { return ’’; } while ($row= $modx->db->getRow($rs)) { $resource[]= $row; } return $resource; } //------------------------------------------------------------------------------------------------- ?>n_id field to database table!"; ?>
Fatal error: Call to undefined function: createtable() in /data03/virt11978/domeenid/www.mydomain.com/htdocs/new/manager/includes/document.parser.class.inc.php(705) : eval()’d code on line 589
Could anyone shead some light. Or has anyone had a similar problem..
thanks. lach.
hmmh, the line number sounds off to me.. is there a possibility that your files could have corrupted on upload? try to upload the files again (and re-paste snippet code in manager). Also, make sure that all files are copied into right places as stated at installation instructions.
"He can have a lollipop any time he wants to. That's what it means to be a programmer."