Stevish

Here is the notice from Microsoft about this. This will affect our ability to use the plugin.

https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online

Thanks for all your work on this, Wayne. I hope this turns from an annoyance to an opportunity for you as you try to rework the email authentication part of the plugin. I know I really love using Google’s newer authentication methods for my own apps, but it was a pain and a half setting it up the first time.

This is also the case for Microsoft email accounts. So it’s not only gmail that has the issue.

Thank you! That appears to have done the trick~

• This reply was modified 6 years, 4 months ago by Stevish.

Thanks for the quick reply. Let me know if/when you roll out a fix and I’ll do some testing to make sure it works in our case.

Ok, it turns out the MySQL error was unrelated. I was able to track down the issue though. When I was moving the images, the field TB_action was not being set. This seems to be because the javascript function set_tb_command in class-ngg-manager.php on lines 245-247 was looking for a hidden field with an ID of TB_action to set the value to move_to:

jQuery('#' + id + "_dialog #TB_action").val(command);

This was failing because the hidden field with the NAME TB_action had no ID set. I modified line 128 to add the ID:

<input type="hidden" id="TB_action" name="TB_action" value="">

Is it possible for you to make this update in your core so that this doesn’t break again whenever we upgrade?

• This reply was modified 8 years, 1 month ago by Stevish. Reason: Fixing formatting
• This reply was modified 8 years, 1 month ago by Stevish.

I am also getting MYSQL errors. Here’s one when I try to move images from one gallery to another:

WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1 for query SELECT t.*, tt.* FROM wp_646_ngg_gallery AS t INNER JOIN wp_646_ngg_pictures AS tt ON t.gid = tt.galleryid WHERE tt.exclude != 1 ORDER by pid DESC limit 0, made by NGG_Gallery_Widget::widget

I’m running WordPress 4.7.2

I agree bubblymaiko is a little rough, but the plugin author is being a little sneaky about adding backlinks to himself and getting free advertising out of us. It’s his right to add attribution to himself in his own plugins, but he should be more upfront about it. Instead, he hides links on your site inside of HTML comments so you don’t know it’s happening. It’s pretty dishonest if you ask me.

Upon further investigation, I’m not finding any hidden ads or links on my site. Looks like if Renzo was guilty of this a year ago, he’s changed his practice. Everything looks like it’s on the up-and-up as far as I can tell. Even the “Include link in footer” setting is unchecked by default. Thanks for a great plugin, Renzo.

• This reply was modified 8 years, 3 months ago by Stevish. Reason: Found more information

Oh, and thanks for the new filters, they’re working great!

Thank you, sir.

Shiny! Updating Postie and playing with the new features is on my list of things to do today or tomorrow.

Yeah, I think that would be workable!

The reason postie_post_before won’t work for me is that the #img%# tags are already processed by then. This means I can’t differentiate between images that were placed at the top by the user on purpose, and images that were placed at the top because the user didn’t add an image tag anywhere else.

I really do want postie to convert the images for me (I don’t want to reinvent the wheel), I just want a way to filter where the extra images (that aren’t placed explicitly with #img%# tags) are placed (specifically, the first one at the top of the post, and the rest at the bottom).

Oh, those apply_filters calls would need to include the $content variable so we could place the images in the content, though I could always accomplish that part through the ‘postie_post_before’ filter… but this would be a little more elegant:

list($pics, $content) = apply_filters('postie_autoadd_images', array('pics' => $pics, 'content' => $content));

Only a LITTLE more elegant, mind, since both parameters would need to be editable and apply_filters only passes the firs argument by reference.

Thanks Chad! Fixed my problem too!

Yes, this was made public just because I wanted to share it with the community, but I wasn’t able to spend the time to make it generic.

Recently, realloc was kind enough to patch the code to include an options page as well as internationalization. The options page (in version 1.3) lets you set the redirect. The other missionary reference would be on the registration form. That can be changed by modifying the language file, or adding a new one. I’m not up on i18n, so I can’t walk you through that process, but a little googling will probably get you pointed in the right direction.