seg-leinad wrote:

Hello everyone!

The CloudReview system has not worked properly over the past few days, and the reason for this is still unknown. Therefore, I have had to temporarily disable this service until it works.

To let you understand a bit about the problem, I'll tell you about how CloudReview works. The system uses a total of 10 cloud variables: 9 store shop data (those variables you see whenever you access your shop's data by using myshops) and one stores pending reviews (user and shop). Whenever I add a review, I use the project with some special features only available to system managers to change the value of that last cloud variable to add the new review, so that whenever the person reviewing opens that project, their computer checks the value of the variable and sees they have a review pending, then starts the reviewing process. After the user has reviewed the shop, that person's computer calculates the new shop rating averages and changes the 9 cloud variables which store their value (and those of the other shops) to include the new ratings.

However, the changes to cloud variables' values while using the project have not been working, for some reason. They do work while the project is still running, but later reset to the previous ones when it is reloaded. They are still recorded in the cloud variable log (for some reason, the last value assigned to a cloud variable in the log does not correspond with the value appearing in the project). There is a way to prevent this from happening, however, but it only works with me, as it consists in changing the value from the project editor by using blocks. This is not possible for the rest as your “edits” to the project will not be saved.

I am going to repost this in the Help with Scripts forum. If I manage to get help we'll be able to reopen sooner, but I do not know if this will be possible.

Thanks for your patience.

No problem, i can wait.

edit : king of the page!

depresso-boiyo wrote:

seg-leinad wrote:

snippy snippy the explanation

Thanks for your patience.

No problem seg, this is still very new and theres going to be trials and errors. We're here to help any way we can and we understand this is incredibly new, so there's going to be bugs

It might not be a CloudReview bug, it looks like it is happening in every single project with cloud variables.

Follow this topic to see the updates on the problem: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/785818/

seg-leinad wrote:

depresso-boiyo wrote:

seg-leinad wrote:

snippy snippy the explanation

Thanks for your patience.

No problem seg, this is still very new and theres going to be trials and errors. We're here to help any way we can and we understand this is incredibly new, so there's going to be bugs

It might not be a CloudReview bug, it looks like it is happening in every single project with cloud variables.

Follow this topic to see the updates on the problem: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/785818/

yeah I'm having issues with my cloud activity check projects. the history is updated but not the variables/lists within the project.

seg-leinad wrote:

Hello everyone!

The CloudReview system has not worked properly over the past few days, and the reason for this is still unknown. Therefore, I have had to temporarily disable this service until it works.

To let you understand a bit about the problem, I'll tell you about how CloudReview works. The system uses a total of 10 cloud variables: 9 store shop data (those variables you see whenever you access your shop's data by using myshops) and one stores pending reviews (user and shop). Whenever I add a review, I use the project with some special features only available to system managers to change the value of that last cloud variable to add the new review, so that whenever the person reviewing opens that project, their computer checks the value of the variable and sees they have a review pending, then starts the reviewing process. After the user has reviewed the shop, that person's computer calculates the new shop rating averages and changes the 9 cloud variables which store their value (and those of the other shops) to include the new ratings.

However, the changes to cloud variables' values while using the project have not been working, for some reason. They do work while the project is still running, but later reset to the previous ones when it is reloaded. They are still recorded in the cloud variable log (for some reason, the last value assigned to a cloud variable in the log does not correspond with the value appearing in the project). There is a way to prevent this from happening, however, but it only works with me, as it consists in changing the value from the project editor by using blocks. This is not possible for the rest as your “edits” to the project will not be saved.

I am going to repost this in the Help with Scripts forum. If I manage to get help we'll be able to reopen sooner, but I do not know if this will be possible.

Thanks for your patience.

Bug fixed! Sounds weird, but it turns out renaming the variables did the job.
Witherplayz still can review The Glow Shop, their review has not yet been completed according to the system.

seg-leinad wrote:

seg-leinad wrote:

Hello everyone!

The CloudReview system has not worked properly over the past few days, and the reason for this is still unknown. Therefore, I have had to temporarily disable this service until it works.

To let you understand a bit about the problem, I'll tell you about how CloudReview works. The system uses a total of 10 cloud variables: 9 store shop data (those variables you see whenever you access your shop's data by using myshops) and one stores pending reviews (user and shop). Whenever I add a review, I use the project with some special features only available to system managers to change the value of that last cloud variable to add the new review, so that whenever the person reviewing opens that project, their computer checks the value of the variable and sees they have a review pending, then starts the reviewing process. After the user has reviewed the shop, that person's computer calculates the new shop rating averages and changes the 9 cloud variables which store their value (and those of the other shops) to include the new ratings.

However, the changes to cloud variables' values while using the project have not been working, for some reason. They do work while the project is still running, but later reset to the previous ones when it is reloaded. They are still recorded in the cloud variable log (for some reason, the last value assigned to a cloud variable in the log does not correspond with the value appearing in the project). There is a way to prevent this from happening, however, but it only works with me, as it consists in changing the value from the project editor by using blocks. This is not possible for the rest as your “edits” to the project will not be saved.

I am going to repost this in the Help with Scripts forum. If I manage to get help we'll be able to reopen sooner, but I do not know if this will be possible.

Thanks for your patience.

Bug fixed! Sounds weird, but it turns out renaming the variables did the job.
Witherplayz still can review The Glow Shop, their review has not yet been completed according to the system.

???? my thing didn't go through? pass the project link

Witherplayz wrote:

seg-leinad wrote:

seg-leinad wrote:

Hello everyone!

The CloudReview system has not worked properly over the past few days, and the reason for this is still unknown. Therefore, I have had to temporarily disable this service until it works.

To let you understand a bit about the problem, I'll tell you about how CloudReview works. The system uses a total of 10 cloud variables: 9 store shop data (those variables you see whenever you access your shop's data by using myshops) and one stores pending reviews (user and shop). Whenever I add a review, I use the project with some special features only available to system managers to change the value of that last cloud variable to add the new review, so that whenever the person reviewing opens that project, their computer checks the value of the variable and sees they have a review pending, then starts the reviewing process. After the user has reviewed the shop, that person's computer calculates the new shop rating averages and changes the 9 cloud variables which store their value (and those of the other shops) to include the new ratings.

However, the changes to cloud variables' values while using the project have not been working, for some reason. They do work while the project is still running, but later reset to the previous ones when it is reloaded. They are still recorded in the cloud variable log (for some reason, the last value assigned to a cloud variable in the log does not correspond with the value appearing in the project). There is a way to prevent this from happening, however, but it only works with me, as it consists in changing the value from the project editor by using blocks. This is not possible for the rest as your “edits” to the project will not be saved.

I am going to repost this in the Help with Scripts forum. If I manage to get help we'll be able to reopen sooner, but I do not know if this will be possible.

Thanks for your patience.

Bug fixed! Sounds weird, but it turns out renaming the variables did the job.
Witherplayz still can review The Glow Shop, their review has not yet been completed according to the system.

???? my thing didn't go through? pass the project link

Sorry for this, but with the system issues we had your review was not saved. Could you please do it again? The project link is https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1055565813/

EDIT: The system does not work yet. Work is being done, but the reason of this bug is unknown. Basically, running a program that sets the value of 9 different cloud variables to the value of their 9 non-cloud corresponding variables only works with one of them.

EDIT 2: The project has been completely fixed. I'll inform Witherplayz of the review they. can upload now.

bump

seg-leinad wrote:

EDIT 2: The project has been completely fixed. I'll inform Witherplayz of the review they. can upload now.

Thanks seg !!

seg-leinad wrote:

(#62)

depresso-boiyo wrote:

seg-leinad wrote:

snippy snippy the explanation

Thanks for your patience.

No problem seg, this is still very new and theres going to be trials and errors. We're here to help any way we can and we understand this is incredibly new, so there's going to be bugs

It might not be a CloudReview bug, it looks like it is happening in every single project with cloud variables.

Follow this topic to see the updates on the problem: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/785818/

I'm going to tell the thing that I keep telling to everyone : hAvE yOu TrIeD ReNaMiNg yOuR cLoUd VaRiAbLeS ???
More seriously, renaming your cloud variables often fix the problem.

Fluffygamer_ wrote:

I'm going to tell the thing that I keep telling to everyone : hAvE yOu TrIeD ReNaMiNg yOuR cLoUd VaRiAbLeS ???
More seriously, renaming your cloud variables often fix the problem.

They said that the project was fixed.

seg-leinad has written. . .

EDIT 2: The project has been completely fixed. I'll inform Witherplayz of the review they. can upload now.

Fluffygamer_ wrote:

seg-leinad wrote:

(#62)

depresso-boiyo wrote:

seg-leinad wrote:

snippy snippy the explanation

Thanks for your patience.

No problem seg, this is still very new and theres going to be trials and errors. We're here to help any way we can and we understand this is incredibly new, so there's going to be bugs

It might not be a CloudReview bug, it looks like it is happening in every single project with cloud variables.

Follow this topic to see the updates on the problem: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/785818/

I'm going to tell the thing that I keep telling to everyone : hAvE yOu TrIeD ReNaMiNg yOuR cLoUd VaRiAbLeS ???
More seriously, renaming your cloud variables often fix the problem.

I actually did like twice. Now it works, but it turns out that did not fix the problem completely. I finally fixed it by adding a small delay between the updates of each cloud variable, and then renaming them to make sure that worked.

seg-leinad wrote:

Fluffygamer_ wrote:

seg-leinad wrote:

(#62)

depresso-boiyo wrote:

seg-leinad wrote:

snippy snippy the explanation

Thanks for your patience.

No problem seg, this is still very new and theres going to be trials and errors. We're here to help any way we can and we understand this is incredibly new, so there's going to be bugs

It might not be a CloudReview bug, it looks like it is happening in every single project with cloud variables.

Follow this topic to see the updates on the problem: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/785818/

I'm going to tell the thing that I keep telling to everyone : hAvE yOu TrIeD ReNaMiNg yOuR cLoUd VaRiAbLeS ???
More seriously, renaming your cloud variables often fix the problem.

I actually did like twice. Now it works, but it turns out that did not fix the problem completely. I finally fixed it by adding a small delay between the updates of each cloud variable, and then renaming them to make sure that worked.

Oh, so scratch team got backward?

Fluffygamer_ wrote:

seg-leinad wrote:

Fluffygamer_ wrote:

seg-leinad wrote:

(#62)

depresso-boiyo wrote:

seg-leinad wrote:

snippy snippy the explanation

Thanks for your patience.

No problem seg, this is still very new and theres going to be trials and errors. We're here to help any way we can and we understand this is incredibly new, so there's going to be bugs

It might not be a CloudReview bug, it looks like it is happening in every single project with cloud variables.

Follow this topic to see the updates on the problem: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/785818/

I'm going to tell the thing that I keep telling to everyone : hAvE yOu TrIeD ReNaMiNg yOuR cLoUd VaRiAbLeS ???
More seriously, renaming your cloud variables often fix the problem.

I actually did like twice. Now it works, but it turns out that did not fix the problem completely. I finally fixed it by adding a small delay between the updates of each cloud variable, and then renaming them to make sure that worked.

Oh, so scratch team got backward?

Sorry? I don't understand what you're trying to say.

I’d like to make a review:

Username: @francisISgodly
Have you ever used CloudReview before? No
Shop to review: The Record Scratchers
Proof of order completion at the shop: https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1087739044
Have you read the CloudReview Terms of Service? Yes
Other: I think this is a cool idea

seg-leinad wrote:

Fluffygamer_ wrote:

seg-leinad wrote:

Fluffygamer_ wrote:

seg-leinad wrote:

(#62)

depresso-boiyo wrote:

seg-leinad wrote:

snippy snippy the explanation

Thanks for your patience.

No problem seg, this is still very new and theres going to be trials and errors. We're here to help any way we can and we understand this is incredibly new, so there's going to be bugs

It might not be a CloudReview bug, it looks like it is happening in every single project with cloud variables.

Follow this topic to see the updates on the problem: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/785818/

I'm going to tell the thing that I keep telling to everyone : hAvE yOu TrIeD ReNaMiNg yOuR cLoUd VaRiAbLeS ???
More seriously, renaming your cloud variables often fix the problem.

I actually did like twice. Now it works, but it turns out that did not fix the problem completely. I finally fixed it by adding a small delay between the updates of each cloud variable, and then renaming them to make sure that worked.

Oh, so scratch team got backward?

Sorry? I don't understand what you're trying to say.

Well scratch team got backward in changes they made, they used to fix this delay needed issue but it looks like they put it back

Fluffygamer_ wrote:

seg-leinad wrote:

whole lotta yap

Well scratch team got backward in changes they made, they used to fix this delay needed issue but it looks like they put it back

Can't believe I have to tell you of all people this, but snip your quotes.

francisISgodly wrote:

I’d like to make a review:

Username: @francisISgodly
Have you ever used CloudReview before? No
Shop to review: The Record Scratchers
Proof of order completion at the shop: https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1087739044
Have you read the CloudReview Terms of Service? Yes
Other: I think this is a cool idea

Review added. Just go to our project (link found in the first post of this thread) and follow the instructions on the screen. Please log in with the account you used to post here: the review will not appear otherwise.

francisISgodly wrote:

I’d like to make a review:

Username: @francisISgodly
Have you ever used CloudReview before? No
Shop to review: The Record Scratchers
Proof of order completion at the shop: https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1087739044
Have you read the CloudReview Terms of Service? Yes
Other: I think this is a cool idea

bumping so it isn't buried

also Fluffy, PLEASE snip your quotes

depresso-boiyo wrote:

francisISgodly wrote:

I’d like to make a review:

Username: @francisISgodly
Have you ever used CloudReview before? No
Shop to review: The Record Scratchers
Proof of order completion at the shop: https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1087739044
Have you read the CloudReview Terms of Service? Yes
Other: I think this is a cool idea

bumping so it isn't buried

also Fluffy, PLEASE snip your quotes

The review was already added, there's no need to bump… Don't worry anyway.

seg-leinad wrote:

The review was already added, there's no need to bump… Don't worry anyway.

i didn't see a response saying it was added, thats mb lol