gjanes

I am planning to implement an option that will process the shortcode returning the HTML instead. This is a planned update in the next release which should hopefully be coming soon.

What OS / character set are you using? I’m wondering if perhaps my editor changed the character set when I did the conversion from 1.5.4?

Can you help me identify a common scenario I can test? Is this a multisite installation?

If I were to guess the cause of the problem -> I’d bet its related to the new pe2-display.css file. It applies some styles to the images in the post, including a border and small pad amount.

This pad that it applies might widen out the table just enough so that only two photos fit per line instead of 3.

You might temporarily try renaming that CSS file to see if that fixes the problem. If so, I could possibly look into an option to either disable that css file all-together, or an option to disable the padding/border.

I’m unsure what to recommend as I don’t own an iPhone.

However, if you do come up with a slideshow method that works well, please provide me the configuration method so I can add it as a configuration option to the plugin.

Please see the related thread:

https://www.ads-software.com/support/topic/how-do-i-insert-an-image-directly-and-without-a-thumbnail?replies=5

Specifically, the change to convert from inserting HTML into the post to a shortcode was done to prepare for Google’s impending conversion from picasaweb to Google+.

The thread I mentioned above is trying to gather information regarding how many people wish to continue the “insert HTML” option. Please weigh in there, although from the amount of interest this may be changed to a configuration option in the near future.

What version of PHP / Apache are you running? I am unable to replicate this issue and wonder if there’s a required version of PHP that this plugin needs to list.

Version 2.0.2 should have resolved this issue. I have resolved this thread, please let me know if you have further problems.

The SSL issue should be fixed in version 2.0.2, please give it a try and let me know – I’ll resolve this issue unless you notify me otherwise.

frenkygo – please start a new support thread and provide me information about your environment. My guess is you may not have the required PHP version.

The plugin *was* by wott, now it’s possibly a collaboration, still hasn’t really been worked out.

I’ll need to update that statement for version 2. ??

Glad that the new version solved the column issue, I’d like to mark this thread as resolved and start a new one for your caption issue.

I have not touched the captions functionality in my development from 1.5.4 to version 2. It is on my list to address as I have time. Please start a new topic for captions, describe the problem in as much detail as you can (I don’t use captions nor am I familiar with the WP gallery).

If you have an example URL of something you want it to do and perhaps another of what its currently doing, it might help me gauge if its something I’ll have time to address, or if it’ll be a larger undertaking.

It may be the fact that you manually changed the URL, which would cause what the plugin thinks the URL is to differ from what Google thinks it is. I’ll see if I can make it detect HTTPS and create the URL correctly to begin with.

I’ll be in touch, hopefully with a bugfix update fairly soon.

You can always temporarily revert to version 1.5.4 which is prior to these changes that may be the cause of your problems.

1.5.4 is the last release prior to the major overhaul release that added the shortcode for images.

That version also has a fix introduced that if you have the “limit size” unchecked, it should insert the image into your blog without any scaling (the scale parameter sent to Google should be s0).

Are there other people who feel the need to be able to get the raw HTML from the shortcode for x-posting?

I was able to reproduce your bug. The root cause is the fact that it clears the dimension textbox when you uncheck the setting and doesn’t properly reinitialize it to a value when you enable it again.

For time being until I’m able to release a bugfix update to the plugin (hopefully soon), if you populate a dimension size and then toggle crop on then back off (if you don’t want it to crop), then save the options, it’ll work again.

It could also be related to the request URL using HTTP when your blog is actually running over HTTPS. I’ll see if I can do a bit of testing with authorization via HTTPS and see if the URL generated for Google needs to differ when running over HTTPS.

I have experience with mixing public and private albums, and it works well. Did you have a previous installation of the plugin prior to 2.0.1 – and if so had you granted private album access?

If so, you might try revoking the access through the plugin and granting it again. There were several fixes applied to the plugin to address issues with Google’s authorization mechanism, and perhaps some of those changes could have affected a previous token, thus causing the authenticated request to Google to fail.

Give that a shot and let me know if you have any success.