Manni02

Okay, will do and I’ll keep you posted (might take me a couple of days as I’m abroad until Friday).

Thanks, I upgraded to the latest version, and it works much better:

1) the field names (email, first and last name) are automatically (and correctly) detected
2) all the users import

There is still one bug though, which that one of the users (the same as last time) is not imported correctly (missing first name and last name).

Not a big problem as it might be specific to my installation if you can’t reproduce.

I see you have released a new 2.0.3 version, is it supposed to address any of the issues above?

Many thanks,

Kind regards,

Manni

Hi Josh,

No problem, glad I could help and thanks a lot for solving this so quickly.

I’ll update the thread after I try the new build.

Best,

Manni

The “forbidden” error is solved.

It was simply due to the fact that on that website, the main wpscst page had not been saved/had been deleted in the settings (the field was blank), so the plugin didn’t know where to go. I suspect the setting was already blank before upgrading to 2.0.2, so I have no reason to believe the saving settings issue is not fully solved.

So to recap, the only remaining issue specific to 2.0.x is that the list of tickets are not displayed when displaying the support page, even when the page is correctly saved in the settings.

The tickets appear fine if I revert to 1.9.x.

Both versions have the issue of not being able to follow the link in the email warning of a new ticket, and give the
You do not have sufficient permissions to access this page.
error message even after logging in as an admin. Maybe I should create a new ticket for that separate issue? Please let me know.

One last update, I compared the file permissions for the plugin folder and files between the two sites and noticed some differences, although they were unlikely to make a difference. The site with the forbidden error had higher rights (755) than the site without the error (705) for the main plugin folder and all the subfolders.

So I made sure all the permissions were the same on both sites (705 for folders and 604 for files) but I still get the forbidden error on one of the site.

I think we should leave this “forbidden” error out until the other issues are solved as it’s probably specific to this installation, and might be due to the fact that I had to copy the plugin manually with filezilla from my backups to change versions.

Another correction, I have reverted to 1.9.x on the website I just did the testing with, and I do still get the “forbidden” message on that website. I don’t get it on the other website.

However, once reverted to 1.9.x, the ticket is created corrected and all the existing tickets appear on the contact page, which isn’t the case with 2.0.x

Not sure if this is related or not, but when I follow the link in the email that informs me (as an admin) that a new ticket has been opened, I can’t access the page from the link, even after I log in as an admin, I get the following message in wordpress:

You do not have sufficient permissions to access this page.

If I then go to the dashboard and access the wpscst panel, I can access everything.

This has never worked, even in 1.9.x, although I forgot to report it.

Hello,

Thank you very much for the quick reply.

The settings saving is solved, so thanks for that!

However, when I create a new ticket (even with the admin which has access to all levels in my website) I get the following error now:

“Forbidden

You don’t have permission to access /wp-content/plugins/wpsc-support-tickets/php/ on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.”

However the ticket is created correctly.

Also, when I go back to my tickets page, the tickets are not displayed, even after a reply is posted.

I have none of this errors with 1.9.x on either of my websites.

Hope this helps,

Best,

Manni

Thanks and done:)

Sounds great, thank you.

I’ve just said this in another post but I really love this plugin, so first thanks a lot for all your good work.

This would be fantastic, as our WP registration process uses double opt-in and activation, so we know that our WP users list is clean and useable.

It would also be great to be able to segment the user list using site roles(for example, we use s2member so it would be nice to be able to target users at a specific membership level, which is achieved using specific site roles like s2member Level1 instead of simple subscriber (which is level 0 / free).

One further extension would be to be able to add a custom field in the user profile for list segmentation. For example, each user has a custom capability field which gives specific access to some of the content. It would also be great to use such field to segment lists further.

If you were able to do this, we would be able to entirely skip Mailchimp for small lists.

Thanks for all your great work!

+1

It would be great to have this option.

Just noticed I made a small mistake in the above review.
When I mentioned the developer’s license, I meant the multisite pro license.
Developers must ask their clients to purchase the pro licence they need (single site or multisite) unless thy run a blog farm in which case there is a specific license for that. There is an affiliate program for developers as well.