Uploading is not available to guests/visitors. To upload, users require a registered user_id and to be recognised by the site. This is actually pointed out in the permissions admin panel.

But… surely if you have a members only site then your users must be registered in some way with WordPress and be able to log in to the site. If they are logged in to the site – then they are logged in to SP. There is no separate registration or login involved.

V5 is completely theme ans template driven. If you investigate the templates in your selected SP theme folder, that message is part of the spHead.php template. The function is sp_LoggedInOutLabel() and you will see the text of the label in that function call. To remove it simply remove the text and leave the empty quotes. Or change it for differemt text.

As always we recommend that you create your own SP theme so that any customisation is not lost during a future update. (http://codex.simple-press.com/codex/themes/theme-basics/creating-a-theme/)

My membership is thru digital access pass, when I log-in as a user that I have set up for my testing it says guest?  So I don’t think its recognizing any user.  If I could get the registration email to work and direct my users to the forum having them register separately for the forum would be fine, problem is it doesn’t work.  Is there someone I can hire to do this for as Ive already invested $39 bucks into this and Im stuck.

Theres no way to allow guests to upload? No bypass?  That would be the perfect solution for me.

as Andy says, simple press does not have users per se…  we simply use the users that are part of the wp site…  and btw, we have several users that use digital access pass (dont know what it actually does but search our forum) with simple press…

what is the problem with the email?  which btw is sent by wp…  If wp is not sending the emails for you, I would recommend a smtp plugin (such as hgk smtp) for wp which often fixes issues with wp sending emails on shared hosting…

afraid we dont allow guests to upload…  seems a bit risky…  and no one else has ever asked for it either…  but it might be possible for you to bypass that protection if you wanted to make a change in your database…

if so, go to phpmyadmin or whatever tool you prefer for database changes… find the sfauths table…  find the auth_name of upload_images and change the ignored column to 0 which wont bypass it for guests… be sure also change the permission in the admin panel to allowed for guests… and see if that lets guests upload…  I have not actually tried it – so might not work… if it does, you could do the same for upload_media and upload_files…

Mark: Is there anything in this thread that might help: https://simple-press.com/support-forum/sp5-general-topics/synchronization-with-wp/

Thanks guys I appreciate the help, yes that thread Im sure will help if those guys respond thanks.  My problem is Im still only recognized as a guest

Well perhaps we are back to WP filter and action hooks. Although as some users DO use DAP apparently successfully I am not sure what to say. But – so you are armed with information I can at least describe the process. In case you do not know it…

WordPress institutes a system of what are called ‘hooks’ which is the method used by plugins to integrate with the WP core. In a way you can think of them as events. When a user registers (using the WP system) it fires an ‘action’ hook that broadcasts to any plugins listening that there is a new user. SP is listening and when that event happens, creates the extra data necessary for that user to be a member on the SP forums.

If – of course, an alternative method of registering a user is employed such as a membership plugin then it is imperative that it also fires the same event hook that Wp would have fired.

On the SP side, new registrants will, by default, be placed in the SP ‘members’ user group although you can set the defaults in the forum admin > Options > Member settings panel.

If all this is not happening, then the first thing to look at is if the registration plugin is actually firing this event hook.