limbus.at

In case this is still present for you, or anybody else:

replace in line 11 of see_style.css
border: 1px solid #D9D9D9;
with
border: none;

As always, a backup of the original file before doing any modification is strongly suggested.

This has to be re-done after each update of the plugin.

= =
Alternatively you may consider creating a child theme, or add custom css code somewhere else if supported by your theme for example. When using this method there’s no need of modifying the original file after each update, but it requires a little bit more knowledge of css.

I have to apologize, I just figured out that another plugin was causing the blank list. After some more testing, because I really needed to re-attach media, I found another plugin giving this problem. Once deactivating that one, “unattach-and-re-attach-attachments” itself was working fine!

Cheers!

Thanks to everybody who was reading this and trying to find a solution.
I could fix it now finally, after I thought already several times before that I found the cause.

Just for the records, if one will find this thread while looking for a solution in a similar situation:

– First, the theme had a major update, so the child-theme didn’t work any more
– Second, the db-export made linebreaks after 1024 chars – though I don’t know if this caused troubles as well, as I was exporting/importing dozens of times this way (copy db-dump to kate, edit urls, import to new db)

– Third, and this was finally the real showstopper, for any reason (must be a configuration combination) better-WP-security was eating RAM faster then I could log into wp-admin to deactivate the plugin. So the server was overloaded all the time and could not load a single page. After renaming the plugin-folder and removing all settings of better-WP-sec. it’s now up again and not consuming that much memory anymore (I think it’s the “Enable File Change Detection” or the automatic backup. I’ll leave both off for now and do further investigation later)

I can confirm this (I’ve tested the next release already).
Thank you very much for your great support, Steve.

(In case one happens to have the style issue which I mentioned in this thread as well, this is caused by plugin- and theme-jquery-conflict. Steve could identify and also provide a solution for this.)

I’m sorry, it just happened again, see here: undefined

This is the source code but I’m afraid this wont help:

<div class="iire_social_shortcode" id="iire_social_shortcode">
<a class="iire-facebook" rel="nofollow" target="_blank" href="https://facebook.com">undefined</a>
<a class="iire-googleplus" rel="nofollow" target="_blank" href="https://plus.google.com/u/0/110362418117155780512/posts">undefined</a>
<a class="iire-twitter" rel="nofollow" target="_blank" href="https://twitter.com">undefined</a><
a class="iire-rss" rel="nofollow" target="_blank" href="https://staging.ubiquarian.net/feed.rss">undefined</a>
undefinedundefined</div>

Lucky I made an export of the table wp_iire_social right before this happened, so I could compare the differences, just some settings (I can send you the tables if you want). I restored the previous values but it still shows undefined.

Anything else I can do? I’ll try to keep it ‘undefined’ until you may check it.

Thanks, I’ve dropped you an e-mail earlier.

Meanwhile I narrowed down the i-issue. It’s only happening with icon-size 32, theme doesn’t matter.

It was the same on the live server, but currently you can’t load the starting page there.
Maybe there was some performance-issue with my host.

Anyway, as I can’t reproduce it any more I’ll put this on resolved.
Thanks.

I have now completely removed the plugin, downloaded the smaller version and installed it via wordpress directly, same here.

In the icons bar, in both settings, it shows the i, in the widget-area as well. But in the shortcodes-bar the image turns to the facebook-f (you can see this on the link I’ve provided in the other post, on the top: the right one is fb, the left one is i, on bottom the same as widget which is fine)

Anyway I’m not sure if I have a problem or a conflict in my installation related with this plugin. When I have the plugin activated and configured the widget or shortcuts for the first time (doesn’t matter which, I tried both as first and only one) the image in the post-sliders-box of my theme moves down-right ~20px. You may see this as well. I can only undo it by deactivating the plugin. When activated again, but not klicked on any settings, it’s still fine. Once settings saved it’s broken again.
Does this make any sense to you?

edit: Don’t know if it is related: when loading the settings you will see one more icon for 1-2 seconds which disappears then, its a white cross on orange background.

The site is not ready yet but you may find it here: https://staging.ubiquarian.net

..of course, after happening yesterday inadvertently at least 10 times and always by the same way, I can currently not reproduce it.

But maybe you can use the link for the other issue as well.

Thank you! Very easy to use.

Thanks a lot for your response, Yani!
I’ve posted on help.time.ly now.

Cheers!

Oh my dear, what’s wrong with me today – again a wrong assignment.
To much testing of so many plugins available.

I’m sorry, please bear with me.

Best regards.

Thanks for your quick reply!

Here is a testing page where you can see my issue:
https://desnobbed.limbus.at/2012/07/essl-5

The main picture is correct, but below instead of eg. 4 small previews is a huge version of the main picture.

When changing the theme to twenty-ten or twenty-eleven it’s working as I expect. With another theme like Kiddies it’s even worse on the main page, it will overlap the right sidebar. If it helps I can change to another theme for testing, on your request.

Maybe it’s just a setting I didn’t set correctly.

Cheers!

I’m really sorry I mixed up two different facebook plugins,
yours is working fine!

Meanwhile I could fix the problem with the token by setting the check to a new link which appeared in the problematic post, the error-message is gone.

The other two mentioned problems are not concerning this plugin.
Again, I apologize.