Hello Sean,

Sorry but looking at the report, there's no where that is pin pointing EasyBlog. Can you please advise me on which of the page that is it referring to?

Trustwave only allows "log in" boxes on https pages. You have a log in box somewhere on your site which displays on http pages. You need to force https on those pages.

Hello Jonathan,

Sorry but a little confused here. Are you referring to our http://stackideas.com site or are you referring to your site? We don't actually run on https

Hi Mark

Pages 28-38 of the attachment detail the Easyblog errors. Hi Jonathan, thanks I will take a look at those login issues.

Hello Sean,

Hm, when accessing the URL that is posted on the pdf, http://www.cannyco.com/canny-company-blog/latest doesn't seem to load up for me. Can you please advise?

Hi Mark

Sorry - I had unpublished the module to see if it passed the scan. Try now.

Hello Sean,

I think you can actually ignore this error message because that error message is complaining that you are displaying a login form without using https:// and since you are not rendering your site with https, there's no way to stop them from complaining. There's 2 work around currently,

1. Enable https for your site

2. Turn off the ability to login for EasyBlog's toolbar. You can do so by heading on to Settings > Layout > Toolbar

Hi Mark

Our site is enabled for https on the shop pages. Because of this we cannot ignore it as without a successful TW scan, we cannot trade online. Will try your 2nd suggestion and see if we pass it, thank you.

Hello Sean,

Hm, why not turn on https throughout the site? This would definitely solve your issues

Hi Mark

I can't do this as it causes issues with other components that are not set up for https. The ironic thing is that Easyblog was working fine, passed the last TW scan no problem and now for some reason, it is highlighting the core Joomla issue and also Easyblog.

Hello Sean,

Perhaps you disabled the login form within EasyBlog? I guess you are now hitting errors on Joomla pages probably because there's a login module somewhere on your other pages?

Hi Mark

We tried the 2nd option from above and that has done the trick. We had a TW scan today and passed so thank you very much for your expert help.

You are most welcome Sean