I did some research, and found that the twitter enable in the backend is not writing the database. This may point at a script missing or bad. Just an FYI

Hey there,

Thanks for the details.

Can you include your site's access and FTP's access so that I can have a better check of it? Make sure there is no space after the last character in your 'Consumer Key' and 'Consumer Secret' after you paste it.

Also, can you provide us with your Twitter developer account access so that we can have a better check on your current configuration for it?

If cannot, can you screenshot the part as shown in the 3 part screenshots so that we can have a better look on your current configuration for it?

Also, make sure your 'Access permission' is Read and Write which is at your Permissions tab.

Thanks for your understanding.

Before we get too deep into this, I wish to correct this error I mention previously. The callback URL in the Twitter Setup of Easysocial is wrong. I have attached screen shot. I cannot find which file generated it, please write back to me with the file I can manually edit to fix this wrong and corrupt callback link. Twitter no longet allows query strings, and you will note the address is also "malformed" .
https://sgecc.org/socialindex.php?option=com_easysocial&view=registration&layout=oauthDialog&client=twitter&Itemid=147

This is what is generated, and does not follow Twitter Callback standards, the query string is no longer valid, and not that there is a missing "/" after the subdirectory "social" so the link is malformed right off the bat.

Let me know the file(s) to check, we will fix this issue before moving on - Thanks a lot

OK I found the file that was not correctly writing the callback URL in the easysocial backend, I edited it by hand for a valid URL, still failing. The back end is still not writing the database with a oauth entry for twitter, but facebook is. I assume it should????

But, here is some screen shots for you, the only one I will not send is the Twitter Key/Api screen, as there should be no requirement to do so. P.S: I will not be able to give you access to the system, as there is secure Dev work being performed, and I would have to file for security Clarence to get you in...

Hey there,

We did release the stable version of EasySocial 3.0.

We had included the fix in it and do you consider to update to the latest version?

If yes, you can update to the latest version of it on your development site first and see if there is any issue that you encountered. You can just copy and paste the new 'Oauth Callback URLs' from EasySocial backend into the 'Callback URL' in Twitter Developer and see how it goes.

Try to regenerate and paste the Keys and tokens IF you still fail after doing what I mentioned.

For your information, you need to set 'Read and write' will do instead of 'Read, write, and direct messages' in the 'Access Permission' section.

If you plan to update to the latest version of it on your live site, you need to perform a full backup on your live site before you update IF there is customization on your live site.

P.S: I will not be able to give you access to the system, as there is secure Dev work being performed, and I would have to file for security Clarence to get you in...

If the issue still persists after the update, can you tell us on what should we do in order to access your site and FTP so that we can have a better check of it?

Also, can you screenshot the 3 parts again that I mentioned earlier so that we can have a better look on your current configuration of your Twitter Developer app?

I screwed up and sent you screenshots from the "old" site. I am now reviewing the new 3.x version, issue still exists.

I did notice one more error I am struggling with. in 3.x the sidebar and most all EasySocial module will not display, and it is not a Joomla issue within the context of templates, I have tried 7 now, same results.

I will post back with more details ... my apologies for directing you to the wrong version

I am going to allow this ticket to be closed, I have the oauth running for Twitter... will open new ticket for other 3.x issues. Thanks

Thanks for updating us on this Brian, will lock this ticket for now to avoid any further confusions. If you do encounter any issues with 3.x, please feel free to start a new ticket. Thanks!