Once this template is set-up to match your classifieds file output, follow the following instructions for text-only classifieds. If you have images associated with your classifieds, you’ll need to upload a zip of your text and images to FTP at a similar time every day and we’ll configure a scheduled automatic process to import these files.

Once your template is setup and we’ve tested & confirmed a correct classifieds import, these are the instructions you will follow going forward:

1. Go to “All Import” on your backend dashboard and select “New Import”.
2. On the “New Import” screen, upload your file.
3. A box will then appear – select “New Items” and then select the type of content you’ll be creating from the drop-down box below – in this case, it will be “Classifieds”.
4. Click “Continue to Step 2”
5. Don’t do anything on the Step 2 page – just click “Continue to Step 3”
6. On Step 3, scroll to the bottom of the page and click the drop-down that says “load template” and select “Classifieds” – this is the template we have created for your file to import the right information to the right places.
7. Click “Continue to Step 4”
8. Do nothing here but click “Continue” at the bottom of the page.
9. On this final page, click “Confirm & Run Import” to import your latest classifieds.

The post Classifieds Text File Import first appeared on Our-Hometown.

Along with the User CSV upload user interface, you can also select if you want to send new members their usernames and passwords. If checked, then MemberPress will automatically send each new user their username and password.

Download Sample Users CSV

Important Note: Importing a User CSV file will NOT and CANNOT associate the user with any memberships in MemberPress. To do that you’ll need to create either a single transactions CSV file for one-time subscriptions, or both a subscription and a transaction CSV file in that order.

Required Columns:

• username — This is the User’s user_login / username field. This is just a small text
• email — This is the User’s user_email. This must be a properly formatted email or the record could fail

Optional Columns:

• role — This is the WordPress user role. Can be ‘subscriber’, ‘contributor’, ‘author’, ‘editor’ or ‘administrator’. Defaults to ‘subscriber,’ even if you don’t specify otherwise with this column header.
• password — Allows you to set the users password. This password will be encrypted/hashed and stored in the database.
• first_name — First name of the user. Can be any small string of text. Defaults to blank.
• last_name — Last name of the user. Can be any small string of text. Defaults to blank.
• website — Website for the user. Can be any small string of text. Defaults to blank.
• address1 — Address Line 1 for user. Can be any small string of text. Defaults to blank.
• address2 — Address Line 2 for user. Can be any small string of text. Defaults to blank.
• city– City for user. Can be any small string of text. Defaults to blank.
• state — State for the user. Can be any small string of text. Defaults to blank.
• zip — Zip Code for the user. Can be any valid zip code string. Defaults to blank.
• country — Country for the user. Can be any small string of text. Defaults to blank.
• *usermeta* — Use the slugs for the Custom User Information Fields you created in the options here to import custom meta for your members.
• registered — The registration date of the user. Must be in format “YYYY-MM-DD hh:mm:ss”. Defaults to the current time during import.

If the username of the user already exists in the system then the user record will be updated with the information in the CSV file associated with the username.

The post Memberpress > Importing Users first appeared on Our-Hometown.

Download Sample Transactions CSV

When to Import This File Type:

• To import a One-Time Subscription – One-Time Subscriptions do NOT need to have an associated subscription imported because “one-time subscriptions” are really just a single transaction.
• To activate a previously imported Recurring Subscription – Recurring Subscriptions are only marked as active (meaning the user will have access to your protected content) when a completed non-expired transaction is present.

Required Columns:

• username or email– The username or email address of the user that should be associated with the transaction. Must belong to an already existing user in the database.
• product_id — The ID of the Membership that this transaction is for. Must be the ID of an already existing Membership in the database.  The id can be found in the url when editing the Membership .  For example the Membership id in this url: http://awesomesite.com/wp-admin/post.php?post=10&action=edit is 10.
• amount — Price of the Membership. Can be any number in decimal format without a currency symbol — for example: 5.99 …
• total — Price including tax (if any). total = (amount + tax_amount). If no tax, this should be set to the same value as the “amount” field.

Optional Columns:

• sub_num — The subscription number that references the subscription. This sub_num must reference an already existing subscription in the database. Defaults to blank.
• payment_method — The unique id of the payment method .. this can be found in the payments tab of MemberPress options. Defaults to ‘manual’. If you’re importing Free members you can also set this to ‘free’.
• coupon_code — The coupon code of the coupon applied to this transaction. Must reference a coupon that already exists in the database. Defaults to blank.
• send_welcome — Controls whether the user will receive a welcome email along with this newly created transaction. Can either be 1 for true or 0 for false. Defaults to 0.
• trans_num — The gateway’s transaction number. Can be any small string of text. If blank, a random id will be generated.
• tax_rate — The tax rate in %. Example 5% should be entered as 5.000. Defaults to 0.
• tax_amount — The amount of tax applied towards the total. tax_amount = (amount*(tax_rate/100)). Defaults to 0.
• tax_desc — The description for the tax. Defaults to no description.
• tax_class — Not used in MemberPress currently. Defaults to ‘standard’.
• status — The status of the transaction. Can either be ‘pending’, ‘complete’ or ‘refunded’. Defaults to ‘complete’.
• created_at — The date this transaction was created. Must be in the format “YYYY-MM-DD hh:mm:ss”. Defaults to current date.
• expires_at — The expiration date of the transaction … when a transaction expires it must be renewed by the user for them to continue to have access. Must be in the format “YYYY-MM-DD hh:mm:ss”. Defaults to Lifetime Access if left blank. IMPORTANT NOTE: If you don’t want your user to have lifetime access based on this import, you have to add an expiration date via this column.
• ip_addr — The User’s IPv4 or IPv6 Address. Defaults to empty.

The post Memberpress > Importing Transactions first appeared on Our-Hometown.

Required Columns:

• name — Name of the Membership. Can be any small string of text.
• price — Price of the Membership. Can be any number in decimal format without a currency symbol — for example: 5.99 …
• period — Number of weeks, months or years. Can be any valid whole number if the period_type=’months’ or period_type=’weeks’ but anything else, this can only be 1.
• period_type — This is the period type. Can be ‘weeks’, ‘months’, ‘years’ or ‘lifetime’.

Optional Columns:

• trial — Sets whether or not the Membership has a trial period. Can be 1 for true or 0 for false. Defaults to 0.
• trial_days — Number of days the trial will last. Can be any whole number. Defaults to 0.
• trial_amount — The amount that will be charged to start the trial. Can be any number in decimal format without a currency symbol — for example: 5.99 …
• group_id — The group_id (which should already exist in MemberPress) of the group that the Membership should belong to. Must be the ID of a valid memberpress group. Defaults to 0 (which indicates no group).

The post Memberpress > Importing Memberships first appeared on Our-Hometown.

CSV stands for “comma separated values,” which is a very common format used by Spreadsheets. You can create a standard spreadsheet in Excel, Numbers, Open Office, or Google Spreadsheet and then export a CSV file from your spreadsheet.

The CSV file must be in Windows Format.  We are working on a fix so this won’t matter, but for now, only Windows CSV format will work.

All of the importers require their own unique data items to be present in the CSV file, but they will all follow a couple of conventions:

1. Each CSV file must have a header row (first row of the file) which contains the name of the field. Everything in the column under the first row will be flagged as being a value for the field defined in the header.
2. The columns of the CSV file don’t need to be in any set order. The data fields are determined not by order but by the header name.

Importing your CSV file

Only one CSV file can be imported at a time, and many of our CSV file types depend on data already being imported into MemberPress. This means that there’s a definite order you should import your files in. Here’s a quick breakdown of what data depend on elements from other data.

In other words:

• Users & Memberships CSV files have no dependencies
• Coupons & Rules CSV files depend on Memberships already being imported
• Transactions & Subscriptions CSV files depend on both the Users & Memberships data already being imported — and optionally coupons that have already been imported. Also transactions & subscriptions may also rely on the id of a payment method setup in MemberPress -> Options -> Payments.

WARNING: Make sure that the data you are importing hasn’t already been imported because, other than the users CSV file, the CSV file will be imported, duplicating the data already present.

The post Memberpress Imports > Intro first appeared on Our-Hometown.

When to Import This File Type:

• To import a One-Time Subscription – One-Time Subscriptions do NOT need to have an associated subscription imported because “one-time subscriptions” are really just a single transaction.
• To activate a previously imported Recurring Subscription – Recurring Subscriptions are only marked as active (meaning the user will have access to your protected content) when a completed non-expired transaction is present.

Required Columns:

• username or email– The username or email address of the user that should be associated with the transaction. Must belong to an already existing user in the database.
• product_id — The ID of the Membership that this transaction is for. Must be the ID of an already existing Membership in the database.  The id can be found in the url when editing the Membership .  For example the Membership id in this url: http://(yoursite).com/wp-admin/post.php?post=10&action=edit is 10.
• amount — Price of the Membership. Can be any number in decimal format without a currency symbol — for example: 5.99 …
• total — Price including tax (if any). total = (amount + tax_amount). If no tax, this should be set to the same value as the “amount” field.

Common Optional Columns:

• expires_at — The expiration date of the transaction … when a transaction expires it must be renewed by the user for them to continue to have access. Must be in the format “YYYY-MM-DD hh:mm:ss”. Defaults to Lifetime Access if left blank. IMPORTANT NOTE: If you don’t want your user to have lifetime access based on this import, you have to add an expiration date via this column.
• status — The status of the transaction. Can either be ‘pending’, ‘complete’ or ‘refunded’. Defaults to ‘complete’.
• send_welcome — Controls whether the user will receive a welcome email along with this newly created transaction. Can either be 1 for true or 0 for false. Defaults to 0.
• sub_num — The subscription number that references the subscription. This sub_num must reference an already existing subscription in the database. Defaults to blank.
• payment_method — The unique id of the payment method .. this can be found in the payments tab of MemberPress options. Defaults to ‘manual’. If you’re importing Free members you can also set this to ‘free’.
• coupon_code — The coupon code of the coupon applied to this transaction. Must reference a coupon that already exists in the database. Defaults to blank.

Other Optional Columns:

• tax_rate — The tax rate in %. Example 5% should be entered as 5.000. Defaults to 0.
• tax_amount — The amount of tax applied towards the total. tax_amount = (amount*(tax_rate/100)). Defaults to 0.
• tax_desc — The description for the tax. Defaults to no description.
• created_at — The date this transaction was created. Must be in the format “YYYY-MM-DD hh:mm:ss”. Defaults to current date
• ip_addr — The User’s IPv4 or IPv6 Address. Defaults to empty.

The post Memberpress > Importing Bulk User Transactions first appeared on Our-Hometown.