[apeterka]

The error log is created by bps pro plugin. php version appears to be 5.2

[apeterka]

Downloaded and installed current version and still see this error repeating daily. Just once about the same time each day. Now the error points to eMember_auth_utils.php instead of utils2.php

[apeterka]

I’m not familiar with LibreOffice. Looks interesting. The CSV does open fine in Google Drive as a spreadsheet. That will work. Thanks for all the help!

[apeterka]

Thanks wzp. Those didn’t actually help, but this discussion seems to indicate others have this problem too:

[http://stackoverflow.com/questions/6588068/which-encoding-opens-csv-files-correctly-with-excel-on-both-mac-and-windows]

[apeterka]

So, my last post got me thinking, and I opened the CSV with textedit on the Mac instead of Excel. The characters appear fine in textedit. Perhaps this is an Excel issue?

[apeterka]

I just updated to v8.8.3. Here is my Chinese name: 裴爱伦

I’ve only tested this myself with a Mac opening the CSV file… if that makes a difference.

Thanks, Alan

[apeterka]

I think I am missing something. When members become inactive, their roles stay the same as far as wp/bbpress is concerned. I’ve tested this on the site, and as an inactive member (logged in Subscriber), I can still post and reply to topics.

[apeterka]

Never mind. I figured it out. Thanks for making the column in the same products table. That made it easy!

[apeterka]

I may have just figured this one out. If I choose Save As… > Windows Comma Separated (.csv), then it seems to import as expected. The Mac default Comma Separated Values (.csv) did not seem to work for me.

[apeterka]

Ok, thanks for that clarification. Our membership dues are oddly based on annual gross income of the member, so subscriptions won’t work too well — members might need to adjust the dues they are paying on a yearly basis.

I think I am back to using a non-expiring member levels, and then moving members to a Former Member group either manually at years end, or automatically with the Auto-Upgrade feature. If I take this route though, will I need to create new member levels every year? And then adjust the eStore button(s) to point to these new levels? I keep thinking there might be a way to re-use membership levels to minimize admin management time. The fact that some members might want to pay their dues prior to current dues expiring though has me thinking admins will need to be involved every year.

Here is what I’m thinking:

Create Membership 2012 level

Create Former Member level

At end of year, move all Membership 2012 members to Former Member

Create Membership 2013 level

Create new eStore buy now buttons for new levels

Rinse and Repeat

Or is it possible to mark everyone in the 2012 level as expired at year’s end? Then perhaps I wouldn’t need to Former Member group.

Sorry so many questions invading my brain!

[apeterka]

Where can I find the code that shows the login widget? I would like to hide/remove the Your Account Expires: line.

[apeterka]

Ok, thanks. I don’t see a way in bbPress to specify roles that can access forums, but this is a bbPress forum question perhaps, so I’ll post it there.

[Author]

Posts