blogger323

I should have written as ‘#widget1_id, #widget2_id’ to avoid confusing expression…

Hi Thermador,

Great thanks for your comment and detailed suggestions.

For the first suggetion, I think you can do it by setting ‘Custom Widget Selectors’. Please try to set it like ‘#area1_id, #area2_id’. It will work for you. (I admit that I have to improve the documents…)

Regarding the second suggestion, it sounds good. I will make it in the future release, hopefully the next one.

Additionally, if you have many revisions in your huge blog, please check my another plugin, Thin Out Revisions. Hoping you will like it and give me another suggestion ??

After a week of no response, I’d like to mark this as resolved, though you can still make additional questions, of course.

After a week of silence, I’d like to mark this as resolved.

With SWE, if you make your sidebar shorter than the height of the browser screen, it will be just fixed.

After the investigation, I found that both the sidebar element and the content element of the Legenda theme have a float=left attribute. It results in the broken layout when the sidebar is fixed.

It’s sad to say, but it’s difficult to use SWE in the Legenda theme.

We should use an ID to identify a single element in a page because a class implies that there are multiple elements to be applied to. And usually it’s easy for theme developers to add IDs in their themes. So I have no plan to add the class-based-identification for the sidebar.

You should learn the theme file hierarchy. Theme developers often put common parts, like a sidebar, in a separated place from single.php. Is there any files named like sidebar.php?

Then, you still have difficulty to find where to modify, you can reach me by send a mail to blogger323 at gmail.com and show me theme files.

Thanks for your feedback. Any feedback energizes the author much more than silence ??

You need to add IDs in your theme.

<div id="mycontent" class="page-content sidebar-position-left responsive-sidebar-bottom">

<div id="mysidebar" class="span3 sidebar sidebar-left">

Then, set options as ‘mycontent’ and ‘mysidebar’.

Happy to hear that. And now you can disable the test account for me.

I’d like to mark this topic as resolved.

After the investigation, I found that I had to adjust TOR for IIS environments. In short, TOR were trying to use HTTPS in the HTTP environment.

I’ve fixed TOR and will release it as version 1.7.2, soon. Check it, please.

Thanks again for preparing the test environment, Viioir. And I hope this fix also helps BarbaraAS’s case.

Viioir,

Thanks for preparing the site. I’ll check the issue.

Or the host name you entered in the browser might not match the one in your certificate. Anyway, it seems related to SSL certificates.

From the response you gave, I assume that you are using HTTPS without having a valid certificate in your certificate store, isn’t it? If you get certificate warnings when you browse your site, it’s true.

This will be fixed by installing your server certificate in your certificate store on the client.

Viioir,

Showing ‘0’ is a good sign. It seems different from BarbaraAS’s case.

Could you check the response from your server by ‘Developer Tools’ I explained in the first post?