baldure

Ditto again. Emails get sent, but without attachment. Then I tried the non-email version, to …htdocs/wp-content/plugins/better-wp-security/backups. No backup.

I don’t know if it is related but it seems like the data itself is causing some errors.

If I select the “data” directly from the db, and try to unserialize it, some rows return an error.

SELECT data FROM wp_6_vfb_pro_entries WHERE entries_id = 201

Yet I can select and view the same record in the VFB interface “…wp-admin/admin.php?page=vfb-entries&action=edit&entry=201“

Is the export function more strict than the edit/view function ?

You’re the man!
This works for me!
Thanks!

I also have problem with 2.2, but a different error message:

XML PARSE ERROR:  Malformed or illegal attribute name
  Error occurs at or below this element stack:
    <ss:Workbook>
     <ss:Worksheet>
      <ss:Table>
       <ss:Row>

I can get the data out with CSV allright, but that’s not the same is it?
And in excel I can’t seem to get the encoding right for the CSV file, all my special icelandic letters get messed up even if I try to open it as UTF8.

I can however open the CVS file in Libre Office with the right encoding!

I see the excel problem both on my Mac and on a Win7 box.

Hi guys.
Thanks Matthew for a great plugin and good support.

But I am also having problems opening a exported xls file.

Client: iMac, OSX 10.8.2, excel 2011 v14.1
VFB version: Pro 2.1.2

The error I got was:
XML ERROR in ExcelWorkbook description
REASON: Bad Value
FILE: wp2013feb.vfb-pro.formpro.2013-02-21.xls____________________
GROUP: Cell
TAG: Data
VALUE: 2013-02-21 08:54:30

Therer was no “T” so I added it in the exported file, and afterwards the file could be opened in excel.

I have a client which has a very big dataset and cannot open and modify every xls file.

Is there some news on a fix?

Well done, this worked!

Best Regards
Baldur.

When I use a csv file containing:

"user_login","user_email","user_pass","first_name","wp_2_capabilities","wp_2_user_level"
"gbs18","[email protected]","$P$BjoKdsT40gH4XUEhsVH96SYQ7TVIff0","Gunnar B Svavarsson","a:1:{s:10:""subscriber"";s:1:""1"";}","0"

I get

s:32:”a:1:{s:10:”subscriber”;s:1:”1″;}”;

in the wp_2_capabilities field in wp_usermeta.

Same result comes from

"gbs18","[email protected]","$P$BjoKdsT40gH4XUEhsVH96SYQ7TVIff0","Gunnar B Svavarsson","a:1:{s:10:\"subscriber\";s:1:\"1\";}",0

or

gbs18,[email protected],$P$BjoKdsT40gH4XUEhsVH96SYQ7TVIff0,Gunnar B Svavarsson,a:1:{s:10:"subscriber";s:1:"1";},0

I’m having trouble importing users into a multisite setup.

I’m trying to set the value ‘a:1:{s:10:”subscriber”;s:1:”1″;}’ into ‘wp_2_capabilities’, but it always gets mangled in the database.
I’ve tried various combinationsof quotes; no quotes, quotes escaped with ‘\’ and with anoter doublequote, as stated in RFC4180.
I can correct it in in my development database and make it work, but I don’t have the same access to the production database.

Any ideas?

Best regards
Baldur