Forum Activity for @michael

Duplicates and 'follow_unique' in jrdiscussion_follow_topic

Jamroom Developers

threaded (anything) isn't highly used.

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

Its something about "US East (Ohio)" that's the problem. Try "Asia Pacific (Tokyo)", it works for me.

I found that the same AWS Access Key and Secret, but a different region for the bucket caused that error message to show or not show.

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

The error I'm seeing come back during test connection is:

at first glance it appears to mean there has been an upgrade of their S3.php script. doing some testing now.

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

If you want to send your amazon keys to support at jamroom I can try them on my site, see what results I get.

But then would recommend generating new keys because those keys wont be secret anymore.

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

my settings look like this, seems to be working on my site. Not sure what the error is for you, hard to say.

--edit--
what action are you taking that triggers the error?

updated by @michael: 11/22/17 01:00:12AM

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

make sure your S3 Access Key and Access Secret Key are set correct for the S3 bucket.

The error happens when jamroom tries to verify that it can write to the S3 bucket.

The full message should be:

Duplicates and 'follow_unique' in jrdiscussion_follow_topic

Jamroom Developers

you can use the ACP -> MODULES -> DEVELOPER -> DEVELOPER TOOLS -> TOOLS -> DATABASE ADMIN to open adminer and export just the tables you're interested in, then import them into your development site.

otherwise paul should be back around later on in the day.

Duplicates and 'follow_unique' in jrdiscussion_follow_topic

Jamroom Developers

From memory: There should only be one pair per topic and the state of the button being displayed toggles the state. So in a perfect world if the user is following the button shows them following, if the user is not following, the buttons shows them not following.

I think somewhere duplicates were slipping in ( maybe caching not showing the correct state of the button, not sure, vaguely remember something. ) and so the delete all records was added.

As for the follow_unique, I believe thats so that the correct follow can be deleted via things like an email link. if links like
.../.../.../remove_follow/user_id=1/topic_id=1 worked it could allow for someone who did not own that follow removing another person from the following list.

If you know steps that consistently add duplicates I can go look at the code again.

disalow periods in user names

Suggestions

When a user signs up with a profile name like:
The points are removed for their profile url, it becomes /onepointone/

If someone else tries to signup with the points in different locations, they get told that profile url is already in use

Border/frame in celebrity skin

Design and Skin Customization

forum question: how to adjust the CSS in Celebrity Skin