The PlugIn does not work with WP Minify!

In version 3.2.4.2 I'm getting PHP Notice: Undefined index: HTTP_X_OPERAMINI_PHONE in wp-content/plugins/sexybookmarks/includes/mobile.php on line 36 and PHP Notice: Undefined index: HTTP_ACCEPT in wp-content/plugins/sexybookmarks/includes/mobile.php on line 38

I know these are just notices, but it would be nice if they were fixed. Thanks.

Hi Josh,

I've received the warning messages:

"WARNING!

* Your theme has the call to but it is not called directly before in the file "footer.php"

This is required to ensure that SexyBookmarks will work properly."

I'm using thesis v1.7 and couldn't find the footer.php. Please help.

Hi,

greetings from the beautiful island La Palma in the canaries. I hope nobody had asked this b4, because I do not want to waste your time, but do you plan to add Google Buzz to the list ?

regards

Joe

Thanks for the plug in, works great.

Hmm, that is strange... 755 should have been sufficient enough to allow the plugin to do it's job. 777 is kinda "ify" I guess for most people, as it's revered as a "hack me" sign... However, I'm not sure how much damage someone could do with your plugin's css folder.

busy is definitely an understatement

Hi Kerem,

We're going to be removing the md5 hash from the filename in the next release, so it will stay as a "static" file name... That way you can make sure it's excluded from your minification plugin.

Ha! Love the picture! Looks like folks are keeping you busy Josh!

Yeah, I don't need to minify Sexy Bookmarks, but also I can't remove it from WP-Minify in an easy way. If only you should disable the random css name :)

Also while I don't need to minify SB, it is better to combine all js and css files in one file to minimize HTTP requests, so while creating a constant css name, merging the style.css into that constant named css instead of importing it would be wonderful, so that WP-Minify can still combine SB's js and css into that big file it creates.

It seems like I said the same thoughts in another way :D

Hi Josh,

Got here a little late for 3.0.1 but still managed to download it from the wordpress repository. I always like to try new things so even you reverted back to v2.6.1.3 I thought I will give a try to v3.0.1.

The only error i got was that of permission (my fault because i forgot to chmod). It didn't go away with changing to 755. Being familiar with "server security fanatics" (lol) tried to chmod 777 and that resolved everything. It's working like a charm now.
Didn't get any other errors except the permissions issue.

Ben.

Had the same problems but chmod-ing to 777 solved it.

Thanks....

SexyBookmarks is Really Sexy....

Hmm, if you get the same errors with v2.6.1.3 then that's a whole different story entirely. I'll email you soon with some more details and things for you to try... For now, I'd just disable the plugin though. Sorry!

WOW! Thank you that was so quick Josh. I read the above comments, but they seemed like different error msgs. Obviously, this is not my line of expertise. I thought I was adding a new interesting twist :)

I did get the same thing with v2.6.1.3. So I did try that before I bugged you.

Thank you for your time and all of your efforts!!

Josh, I tried to go through a bit more into the problemm but had no luck.
The code is way too much and have no time to build a debug configuration on a vmware or something...
So, I rolled back to 2.6.3 and seems to work fine now. I have a small problem, but nothing serious... I'll check and maybe will come back in a week or something.

Anyway, I did a couple of tests.

If I delete the images folder (the entire folder and ofcourse what is whitin it) and then try to save the settings, looks like it works. I only get a warning specifying to have a look here
http://sexybookmarks.net/documentation/usage-insta...
permissions problems with the css folder.

I checked it with FTP and was all ok.

Then I tried to disable and re-enable the plugin, but still a fatal error was raised. Unluckly, have no warning text or error number to show you. No description, just a "Fatal Error while activating the plugin".

The server (Linux) has a feature that allows me to fix the permissions, all at once, on folders and files. I did it, but nothing changed and I knew it was, because in wp-config-php I added

define ('FS_CHMOD_FILE',0755);
define ('FS_CHMOD_DIR',0755);

some time ago...
so, it doesn't look to me as a problem with folders or files permissions.

Hi Chandra,

It's not a theme issue... that's definitely our goof. It's one of the issues mentioned in the "Update" at the bottom of this post (above the comments). I'd recommend downgrading to v2.6.1.3 until we can get this all sorted back out. AGAIN! haha

Thanks for the gentle natured comment... It's most definitely appreciated. We will get the issues figured out soon, but until then, like I said, you may be better off reverting back to v2.6.1.3

Hey Josh, I know you're super busy and overloaded with people asking and expecting stuff from you...so if you don't have time to help, I totally understand.

But if this is an easy fix? Anyway, I've read the FAQs, all comments and posts back to five versions ago. Downloaded newest version, then went back to the previous, still no love for me.

Have the head tag the way it should be. I've run through any twitter updates (and followed you) but can't figure this out or find anyone that has this listed this issue. I'm guessing it's a theme incompatibility?

Config Panel says:

Warning: Invalid argument supplied for foreach() in /home/content/s/l/b/slblogadmin/html/wp-content/plugins/sexybookmarks/sexy-bookmarks.php on line 339

Warning: array_diff() [function.array-diff]: Argument #2 is not an array in /home/content/s/l/b/slblogadmin/html/wp-content/plugins/sexybookmarks/sexy-bookmarks.php on line 340

And then under functionality setting it says:

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/content/s/l/b/slblogadmin/html/wp-content/plugins/sexybookmarks/sexy-bookmarks.php on line 361
class="hide">

Warning: Invalid argument supplied for foreach() in /home/content/s/l/b/slblogadmin/html/wp-content/plugins/sexybookmarks/sexy-bookmarks.php on line 341

With appreciation...even if you can't get to this! THANKS!

Funny you should be having trouble with a minification plugin considering the latest version of SB comes with a minified stylesheet and minified JS... So there's no need for your other plugin to have to minify it.

Sexy Bookmarks 3.0 is not compatible with Wp-Minify, which is equally important for me as Sexy Bookmarks.

The problem arises in the css file which is generated with a random name. It imports style.css of Sexy Bookmarks, and this breaks minification process.

As a new css file is generated after each Sexy Bookmark preference save, it should be better that it has a standard name (not random, as the css and images folder will be full of these if you change your preferences often) and it would be better if the style.css contents were merged into this file, rather than importing it.

I have removed this file from minification process, but after each SB preference save, I have to find the new file name and add it to WP-Minify.

We can discuss this problem more thoroughly via mail if you like.

Thanks for the great plugin.

Ohh and one more thing... I am trying to use it with thesis theme... maybe that has to do with it !? cause just tried the previous version, 2.6... it also gives errors on the settings page... weird eh?!

Also wanted to mention...

For the past 3 years i've been developing a freeware, the (E)lephant, and that's just what happens mate... People are annoying and always complain like you owe them something... Just take it like and enjoy your project, you don't owe no one anything!!!

Have a nice day.

Yeps... me too mate...

3.0.1 - triggers a fatal error...

I won't say too much, but that looks like the best and most SEXY bookmarking plugin ever !!!

Too bad it doesn't work in the latest version... meanwhile please downgrade the stable version.

http://wordpress.org/extend/plugins/sexybookmarks/...

I know this could be a stupid question, but where can I download a previous sexy bookmarks version? :s
I'm looking for te 2.6.x

"Roll back" simply means to delete your current version from your server and upload an older version.

Couldn't figure out how to roll it back, no option for that anywhere I seen. But I did use a backup of the old one and it's all working now.

Not messing with the coding of plugins. I'll leave that up to the creators :D

My bad, my bad. Sorry.

Hi,
Since the upgrade I can no longer access the configuration panel, I get a "you do not have sufficient permission to access this page" message.

That's if I am logged either as user or as admin. Bit of a problem as all buttons have disappeared from the posts for me too.

haha, well in our defense... It's 100% IMPOSSIBLE for us to test every possible server setup in ever possible hosting company's environment. That's what's causing the issues. However, yes... we will most certainly be doing MUCH more testing before releasing a feature this complex the next time around! haha

well, good one, I saw that sensitive informations right after the submit...
LOL

The next is for both, me and you. :p

http://img89.imageshack.us/img89/3309/dsc00001qe5....

I removed the link to that image because it shows some sensitive information about your server setup. We're working frantically on a solution to this issue as we speak.

Thanks for letting us know.

Major error.
I took a screenshot
[image edited for security reasons]

This happens when saving the settings.

What did I do?
I simply updated the pluging fom the wordpress dashboard. It ended up with a "fatal error, cannot activate the plugin".

Then I went throught this list of comments and checked the server settings. everything is fine, permissions and all the rest.

Feel free to ask me more questions in order to help you out fixing this issues.
In the meantime, I try downgrading to the previous version (2.6.x)

Bye

It works fine! thank you very much!

Ok, that helps a lot… I sent you an email with a possible solution to what you’re having problems with.

I downgraded to 3.0! ;)

Great! Thank you.

I have an idea as to what it might be... Give me a bit and I'll try to get you a customized file so you can see if that fixes the issue.

Really? You downgraded to v3.0 and it works? or did you downgrade to v2.6.1.3? If you downgraded to version 3.0 and it works, then I have a better idea as to where the problem may be!

it's a fresh install on an older site.
I'll try to post a screenshot as I cannot copy&paste from the drag and drop area.

I run wordpress 2.9.1 localized in romanian, fresh installed, only thing I tried was to click on select most popular and save to see if it fixes anything.

I understand! thanks for all your effort, just to let you know, that is definitely a problem related to the new version, cause we downgraded to the 3.0 one and it works fine... ;)

Wow, that's a new one... No, I really don't have any ideas as to why that's happening. Is this a fresh/new install? or an upgrade from a previous version? Are you able to save your settings at all?

I get lots of this errors on the configuration page:
Wrong datatype for second argument in
/..../wp-content/plugins/sexybookmarks/sexy-bookmarks.php on line 215

Instead of icons to rearange are the same errors on various lines of code

any sugestions?

I'm currently looking into it... There has to be a common denominator between all of you who are experiencing this issue. The only problem is that no matter how I setup wordpress, whether in a subdirectory, root directory, or otherwise, I can't recreate the issue in my hosting environment.

This leads me to believe that it's most likely host related. However, I'm still looking into it. Sorry for the inconvenience!

Hi,
we have the same problem in our blog! We use the dezine theme from themeshift.com, and it the plugin used to work, before the update! We did the update, via ftp and tried all solutions you mentioned so far...

Unfortunately, yes. I know that’s a scary prospect, but that’s really the only way I would be able to really debug the issue as I can’t recreate it in my hosting environment no matter how I setup wordpress. Sorry

Alright then. But thank you for your help. Only other oportunity would be to send you my FTP-data?

Unfortunately, it's virtually impossible for us to be able to pre-test a release in order to make sure that every possible server setup is covered.

I'm glad you were able to downgrade to the last stable version before this one to fix your problem. We'll keep looking into what was causing the issue.

Without being able to see the server setup myself, I’m afraid I’m all out of ideas… I’ve mentioned everything that it *could* be, but as I can’t actually see your server (only the website) then there’s no way I can truly debug it.

I guess your best option would be to simply downgrade to v2.6.1.3