I'm having problems with integrating getImageBlock with Drupal.
I'm getting a specific item and using the itemId, etc, etc,... now it gets the block except that the url for the image is wrong.
the url for my section is "website.com/?q=node/6/bodiesofwork" and the url for the image is just adding itself to the url. So I'm getting:
website.com/?q=node/6/bodiesofworkgallery2/main.php........
what is odd is that when I display the whole gallery in the site using handle_request it displays the image correctly. The only place I submit a url is in the gallery_init function and these both use the same function.
with the handle_request I get "website.com/gallery2/main.php...." which works beautifully
What I assume is happening is that the imageblock module is just dumping the url information to the end of the url in the browser. While the handle_request is actually parsing it. Can anybody point me in the direction of where imageblock sets the url for the images?
I racked my brains for a couple of hours looking through the smarty template system and now I feel like I want to jump off of a tall building.
Thanks for the help guys.
Posts: 32509
before calling getImageBlock() you need to call GalleryEmbed::init(..); and the arguments of init() determine the urls.
you need to set the correct embedPath, embedUri, and relativeG2Url
Posts: 3
I'm already calling GalleryEmbed::init(..), and it's working propery for the gallery_handle_request function.
I've set embedUri and relativeG2Url. The embed documents(embed.php) say that you only need to provide emberUri OR embedPath, and it says that it doesn't matter which one to use.
Can you tel me what the difference is between:
embedPath, embedUri, and relativeG2Url
thanks
Posts: 3
You were right! Thank you very much!!!!
The problem was that I didn't have embedPath setup. I did have embedUri and relativeG2Path setup properly though. I just had to set embedPath to '/'
Thanks again.