The final release of G2Image Version 3.0 is out! Please download it here.
A WordPress blog demo is here.
A TinyMCE demo is here.
A standalone demo is here.
Changes (v3.0 vs v2.2.3):
* GUI reorganization.
o Visual directory tree instead of breadcrumbs or HTML selector
o Insertion options on a fixed pane
o Ability to select multiple images for insertion with the current insertion options
* Switched from php array method of internationalization to the standard gettext method.
* Improved LightBox HTML tag by adding a variable slideshow group name (In 2.2.2 it defaulted to g2image)
* Added support for the "exactsize" attribute in the Drupal G2 Filter tag.
* Added "All" as a "thumbnails per page" option
* An added benefit of reorganizing the backend in v3.0 is that G2Image now fully honors Gallery2 user permissions. It picks up the current user's permissions from the Gallery2 session cookie and applies them.
Changes (v2.2.3 vs v2.0)
-Version 2.2.3 fixed a bug where albums with no titles did not show any text in the album selector. It now displays the album directory name if there is no album title.
-Version 2.2.2 fixed a bug in v2.2 and v2.2.1 where thumbnail and fullsized image URLs were incorrect if the Gallery2 directory was not /gallery2/
-Version 2.2.3 works with Gallery2 2.1 or higher. (Version 2.2 required G2 2.2. Thanks to Suprsidr and Valiant for helping to make it backwards compatible with G2 2.1.)
-Eliminated use of G2 ImageBlock call in the backend. This eases getting information about a Gallery2 item.
-Updated the Album selection so that it loads all albums in a tree and automatically reload the page on album selection.
-Added support for a LightBox HTML tag and fullsized image HTML tags.
-FCKEditor integration
-Cleaned up the GUI a little (made the "sort by" and "images per page" select boxes force a redraw automatically instead of requiring another button press.)
Notes:
-G2Image 3.0 requires Gallery2 2.1 or higher
-Wordpress users should download the WPG2 v3.0 SVN snapshot, which includes G2Image 3.0 in its entirety. G2Image 3.0 is not backwards compatible with WPG2 2.1 or earlier.
-Joomla JCE users should leave the file zipped and install it using the plugins manager under the JCE component.
Thanks to all who contributed ideas, language files, and beta testing,
Kirk
Posted: Sun, 2007-09-16 11:14
Posts: 1
Works great except the "thumbnail with link to image" has an incorrect path. Clicking on the thumbnail image takes me to the following URL:
http://mywebsite.com/mambots/editors/tinymce/jscripts/tiny_mce/plugins/g2image/g2image.php/index.php?option=com_gallery2&Itemid=26&g2_itemId=10235
It seems that there is some problem with our configuration. Where can I fix the paths?
Posts: 492
Did you set it up by following the Joomla directions here? http://g2image.steffensenfamily.com/index.php?title=Joomla
Posts: 3
In WPG2 2.x there was an option to use either wpg2 or wpg2id tags when inserting images. Is there any chance of getting an option for wpg2 tag behaviour in modern G2Image? I'd very much would like to use Gallery2 paths instead of ID's. Or did I just miss to spot it in the current version?
Posts: 492
We took the "WPG2 tags by paths" option out of WPG2 3.0/G2Image 3.0 on purpose. The wpg2 and wpg2id tag logic are both still in the internals of WPG2 v3.0, but that's only to maintain backwards compatibility for blog entries.
Here is the thought process: if you are using WPG2 tags rather than HTML, it is to maintain good links between WP and G2 regardless of if you change your permalink structure in WP or your URL rewrite structure in G2, etc. Along those lines, if you use the G2 item ID instead of its path, it will always be a good link no matter where you move the image in G2 or how you rename it over time. The ID is constant; the path is not always constant.
Also, because of the way I rewrote the backend of G2Image, it's harder to get the path internally now. In fact, it's impossible for some items. Before, G2Image didn't know about replica items, becuase it was getting it's information from the file system, instead of from G2's database. Replicas aren't stored in the file system, they're only stored once in their original file system spot, and the replica info is only stored in G2's database. Now that G2Image is getting it's item info from the database, it knows about replicas and linked items. These don't have a path - only IDs. They must be inserted into wpg2 tags using their IDs.
So, for all of these reasons, we removed the "wpg2 tag by path" option from G2Image. That doesn't help, but at least explains why it is the way it is.
Kirk
____________________________________
G2Image Documentation, G2Image Demo Page, My Family Website
Posts: 3
Thanks for the explanation. Just to let you know, the reason I like paths better is this: I often write the wpg2 tags with paths by hand in my blog entries. My album hierarchy and filenames are straightforward enough (based on dates) for it to be somatimes faster that way, and it's also more practical with the browser in my phone. It would have been nice to have consistency between the entries written by hand and using G2Image.
Posts: 492
Cool. No problem. The paths will still work. WPG2 will decipher them correctly. Again, for backwards compatibility. So, you're good to go to keep using them.
I understand about the consistency issue. I guess if enough people ask for it, we can add it back in. It's just one less thing to have to explain to new users...
Thanks,
Kirk
____________________________________
G2Image Documentation, G2Image Demo Page, My Family Website