To those using the user lists plugin and complaining about extra slashes, I apologise for not realising that it is because your host must have magic quotes enabled. Please read the php link. The php manual says: Relying on this feature is highly discouraged.
I have looked into it and it seems that because , with it enabled, php adds the slashes at the very last minute (when you click export cvs), there is no way I can stop it from kicking on.
The only possibility may be to write the csv to a file on the server. I specifically do NOT want to do this for non public lists, because
- it is user data and should be kept private, not written to a file on a public server
- plugins cannot easily access ‘private’ folders to keep such a file private
So either you could try seeing if there is a way to switch it off at your host, or do a search and replace in the csv file, or make the list public (if this is ok with your users and your privacy agreement with them)
Ask your host to disable magic quotes ….Or try my very good hosts – they are reliable, helpful. We’ve been with them for more than 10 years now with no complaints.
Pingback: Js/Jquery loaded, but not 'working' (aka widgets frozen) all browsers, no plugins
Hi Anmari, not sure if this is the appropriate place for it, but since it’s the last post related to your wonderful plugin… I think I have a tiny CSS-related bug I found in your User-Lists plugin; it has to do with two image files (gray-grad.png and menu-bits.gif) that are pulled in by the CSS file style.css but return a 404 because they are called in the incorrect directory, namely as follows:
http://www.example.com/wp-content/plugins/images/gray-grad.png
http://www.example.com/wp-content/plugins/images/menu-bits.gif
That should be, instead and respectively:
http://www.example.com/wp-admin/images/gray-grad.png
http://www.example.com/wp-admin/images/menu-bits.gif
Fix is relatively simple, by changing line 59 in style.css to:
background:#DFDFDF url(../../../wp-admin/images/gray-grad.png) repeat-x scroll left top;
And line 181 in the same to:
background:#EEEEEE url(../../../wp-admin/images/menu-bits.gif) repeat-x scroll left -379px;
That should do it – even though I don’t like the ugly traversal up to the wp-admin folder, it’s tested and I have it working on my site.
Thanks for highlighting that – when people wanted “public” lists, I copied the admin css for the table and had not picked up that of course the paths to the images would break. Since I am not a fan of non-essential images, and also would rather that the theme css should determine how the table should look, the next release will
1) exclude the images
2) offer option to switch off the css for the front end – backend is just using whatever admin css is there anyway
PS – to resolve the magic quotes issue, as long as you can see and edit php.ini you’re in good shape; just search for “magic quotes” and as explained here set the magic quotes section to off, as follows:
Worked for me!
First another minor observation, sorry about that: here you refer to the tag users (see link in the text “various posts under users“) but it seems more practical to follow the category of user-lists, instead.
Now my polite little nag: do you still think about supporting custom tables (*cough* CUEF *cough*) for this great plugin?
With more and more being crammed into the user meta table and the risks of plugins dabbling with serialized data that manifest themselves when those plugins are deactivated and don’t clean up properly after themselves leaving that table with legacy, derelict data… It’s why I still don’t use the custom fields of Your Members (or others, not to single just one out – to my knowledge they all stuff user data serialized in the user meta table) but really would like to unleash the power of your AmR User List plugin (e.g. for a directory of current members, with custom fields, who opt into being listed)
Hi – yup I think about it – frequently! It is just that I have a few other projects on the go, but every time you ask, I think about it some more and magically one day I’ll decide to do that instead of something else I should be doing
Maybe even add a cleanup unwanted meta data option?!
re the tag – you are correct will fix – thanks