@ma3ry BuddyPress Xprofile Custom Fields have some security loopholes and it will need dedicated time to fix all issues and make it compatible with the latest version.
@venutius check it once if you have time. It has 6000+ active install, needs some attention.
Which file and line number is the error showing from?
It happens when I run BackWPup. There are no line numbers. It shows up in the logs as follows.
[18-May-2018 09:49:33] Database backup done!
[18-May-2018 09:49:33] 1. Trying to create a WordPress export to XML file …
[18-May-2018 09:49:36] Check WP Export file …
[18-May-2018 09:49:36] WP Export file is a valid WXR file.
[18-May-2018 09:49:36] Compressing file …
[18-May-2018 09:49:36] Compressing done.
[18-May-2018 09:49:36] ERROR: Call to a member function close() on null
[
Is anyone likely to update BuddyPress Xprofile Custom Fields?
It’s not possible, it’s been closed for security reasons, we can only summise that it’s got an issue that the original author can’t or won’t fix. It’s possible that someone could make a fork of it but the problem is WP would not let them inform the installed base.
Wow! That puts me in a real pickle, but at least I know now. Thank you so much!
I’ll talk to my coder about it.
I don’t think the changes I’ve made could have caused that, I only updated the version checking which is internal to the plugin and not referenced by other, and I didn’t change any data that was being recorded in the database. If you deactivate xprofile custom fields, does the problem go away?
Oh no, I’m sorry, I didn’t mean to imply that your changes caused it.
This backup error happened before I made the changes.
Your changes helped me very much!
Ah ok, but you think this is related to BuddyPress?
Yes, I think it is the same issue as the one I originally wrote about re XProfile Custom Fields showing an error on my dashboard.
I got the notification on the dashboard first, then I saw that my backups also had problems. I think both are related to the same plugin.
Your solution helped with the dashboard issue. It is no longer showing.
I think the next thing to do is to deactivate BP then run your backup, see if that fixes it. Then we will know for sure.
Thank you for the suggestion. I deactivated the XProfile plugin first and ran the backup job – still had the error, so I deactivated the BuddyPress plugin and ran the backup job again. I still have the error. I guess I’m going to have to look into this further.
One thing I did notice when I deactivated the XProfile plugin, I retained all my current extra fields. The only one I had a problem with is birthdate. It used to show age, not birthdate. Perhaps there is a plugin that will deal with just this issue. I’ll have to look around.
Thank you again for all your excellent help. I really appreciate it!!!!
Yes, with xProfile once you have configured the field from the plugin, BP remembers those settings so you no longer need the plugin, however you’d need it to add new fields supported by the plugin. I’ve put in a request to include this plugins features in BP core, if that happens you should get the ongoing support that is required.
I guess regarding your backup issue the next step is to check with that plugins support pages and report the issue there. WP also updated at the same time as BP so it’s not inconceivable that the error stems from that.
That would be great (if it were added to BP core).
Re my backup issues I have sent it off to my Systems Admin. He’s a genius at this kind of thing.
Thank you again so very, very much for all your help!
