| Scott Romanowski |
Ditto for events #153336 and #153389. I can't report to either, nor can I edit the session details. (To see what was reported, so I can tell my VC how many people played in each session.) The session numbering on #153336 is also messed up, which may be either a symptom or a cause. The list of sessions goes <blank, no number>, -511, 1, 2, 3, ..., 30, 31, 32, 153336, 153337.
maldar
|
I tried to report my sessions for 154918 last Saturday/Sunday and this morning and just now and I get the following:
Sorry, there was a problem handling your request. The system administrator has been notified.
Please contact webmaster@paizo.com if you continue to have difficulties.
Click here to return to paizo.com
Edit: Just checked all my other Events and I am able to report on all of them. I then created a new Event to see if it was due to the fact that the Event I want to report sessions for was my most recent event. I can report to the new Event but still cannot report to 154918.
| Scott Romanowski |
I'm still having trouble. There's been no reply to my email. While there's been no response here, I saw Robert Brandenburg (software developer) write "We have identified the cause of this issue and it should be fixed in the next major website update, along with a few other issues related to organized play reporting." here.
Randy L. Williams
|
I found that some session names changed after I set up the event and before I could report it. Specifically the Starfinder scenario names have dropped the PDF from the title. Maybe the same thing has happened to some Pathfinder scenarios as well.
To fix it I had to create a new event with the new scenario names, report the re-created event, then go into the old record to clean it up and mark it as completely reported to remove it from my list of events. Convoluted, but effective.
It is amazing how changing something so small can have such a large impact.
| Nicolas Fuchs |
Looks like it's actually not just me.
Cannot report for or view sessions in event 158,154
(report auto-redirects me to http://paizo.com/pathfinderSociety instead)
Doesn't work in Firefox, Chrome, Edge, or Internet Explorer. Looks like it's directing me to a sign-in page and then back to the home page (where I'm still signed in).
Kadasbrass Loreweaver
|
Well its good to see I wasn't the only one having issues, at first I thought I had done something wrong. Lets go ahead and add a small convention to the list of Unable to Report PFS Events, event #157504.
My older events seem to be allowing reporting but from the looks of everyone else it appears that its mostly newer events having issues.
maldar
|
I found that some session names changed after I set up the event and before I could report it. Specifically the Starfinder scenario names have dropped the PDF from the title. Maybe the same thing has happened to some Pathfinder scenarios as well.
To fix it I had to create a new event with the new scenario names, report the re-created event, then go into the old record to clean it up and mark it as completely reported to remove it from my list of events. Convoluted, but effective.
It is amazing how changing something so small can have such a large impact.
I did a lot of tinkering just know and I dated one of my sessions to last year and it works enough for me to be able to report the PFS scenario I had waiting. However, I was not able to report my SFS session. When I click on the drop-down on the reporting page for scenarios it does not show any SFS scenarios, even when I click the Show More Scenarios button all it shows is PFS.
When I tried to edit one of my sessions to reflect the fact that we changed what SFS scenario we were running, the SFS we first listed was still showing even though the checkbox was unchecked and when I doubled checked to make sure, it was indeed unchecked. The SFS scenario still had PDF in the name and still shows PDF in the name.
This leads me to conclude that the error we are having is due to the removal of "PDF" from the names of SFS scenarios.
maldar
|
Maldar, did you select the correct campaign? Under the "Show more scenarios" you should see a drop down box. You first need to select "STAR" there before you see SFS scenarios. It was changed recently as I found out when I wanted to report a SFS scenario.
Thanks, I did not notice that.
GreySector
RPG Superstar 2013 Top 8
|
| 1 person marked this as a favorite. |
Can't report or edit # 155460 either.
There are also two phantom instances of "Starfinder Society Roleplaying Guild Scenario #1-03: Yesteryear's Truth PDF" being listed for this event, one on Dec 29, 2017, the other on Jan 19, 2018.
I can't find a way to delete the date, and there is no way I can see to remove the listing from the event.
FLite
|
| 1 person marked this as a favorite. |
LoPan666 wrote:Can't report or edit # 155460 either.There are also two phantom instances of "Starfinder Society Roleplaying Guild Scenario #1-03: Yesteryear's Truth PDF" being listed for this event, one on Dec 29, 2017, the other on Jan 19, 2018.
I can't find a way to delete the date, and there is no way I can see to remove the listing from the event.
I am having the same problem.
Event # 157142
Shisumo
|
I tried to report my sessions for 154918 last Saturday/Sunday and this morning and just now and I get the following:
Quote:Edit: Just checked all my other Events and I am able to report on all of them. I then created a new Event to see if it was due to the fact that the Event I want to report sessions for was my most recent event. I can report to the new Event but still cannot report to 154918.Sorry, there was a problem handling your request. The system administrator has been notified.
Please contact webmaster@paizo.com if you continue to have difficulties.
Click here to return to paizo.com
Having this exact issue with event #158049.
Doctor Boem
|
| 1 person marked this as a favorite. |
. . . So, is anyone at Paizo IT actually looking at this?
I know that they are anxious to have people keep using the same session IDs so the numbers don't get up to 7 digits -- but this is getting ridiculous.
I'd feel a lot better if I had some idea that someone was actually taking some sort of action. Otherwise, it's time to start creating new events willy-nilly every time, to avoid this stupid problem.
Alanya
|
. . . So, is anyone at Paizo IT actually looking at this?
I know that they are anxious to have people keep using the same session IDs so the numbers don't get up to 7 digits -- but this is getting ridiculous.
I'd feel a lot better if I had some idea that someone was actually taking some sort of action. Otherwise, it's time to start creating new events willy-nilly every time, to avoid this stupid problem.
Doctor Boem
|
Thanks!
Doctor Boem wrote:This was the latest reply in another thread. . . So, is anyone at Paizo IT actually looking at this?
I know that they are anxious to have people keep using the same session IDs so the numbers don't get up to 7 digits -- but this is getting ridiculous.
I'd feel a lot better if I had some idea that someone was actually taking some sort of action. Otherwise, it's time to start creating new events willy-nilly every time, to avoid this stupid problem.
JohannVonUlm
|
I am having problems trying to report a recurring event (event #154907). It's a once a month recurring Starfinder only event. I had managed to report our first two scenarios, but after our latest session, when I try to open it, I get the broken link webpage.
I tried emailing the paizo email given on that page, but have seen no response. I was pointed to this page, but notably no Paizo web folks have seemed to chime in on this thread.
Has anyone found a solution yet?
Robert Brandenburg
Software Developer
|
| 3 people marked this as a favorite. |
I am having problems trying to report a recurring event (event #154907). It's a once a month recurring Starfinder only event. I had managed to report our first two scenarios, but after our latest session, when I try to open it, I get the broken link webpage.
I tried emailing the paizo email given on that page, but have seen no response. I was pointed to this page, but notably no Paizo web folks have seemed to chime in on this thread.
Has anyone found a solution yet?
The fix for this issue will be included in the next major website update in early December, along with other organized play fixes/updates.
The Masked Ferret
|
Cannot report 2 sessions on 155317
Up to 5 sessions now that cannot be reported.
Thanks, Robert, for the update about the timing. I would love to be able to get these tables properly reported.
Eric Collins - France
|
A bit of a different issue, so sorry if this is not the place for it: I am not receiving the correct "tables of credit"for Starfinder Society games I DMed and reported.
I have 16 tables of credit, which corresponds to the scenarios reported so far.
But I never received credit for the two instances of running the AP (Incident at Absalom Station) that I reported.
I have scenarios credited before and after the the APs I reported.
Just wondering if others had the same kind of issue?
| BretI |
| 1 person marked this as a favorite. |
A bit of a different issue, so sorry if this is not the place for it: I am not receiving the correct "tables of credit"for Starfinder Society games I DMed and reported.
I have 16 tables of credit, which corresponds to the scenarios reported so far.
But I never received credit for the two instances of running the AP (Incident at Absalom Station) that I reported.I have scenarios credited before and after the the APs I reported.
Just wondering if others had the same kind of issue?
Others have reported this as well. I’m hopeful that the fix will also help there.
I don’t know if anyone has gotten table credit for Incident at Absalom Station.
maldar
|
GreySector wrote:LoPan666 wrote:Can't report or edit # 155460 either.There are also two phantom instances of "Starfinder Society Roleplaying Guild Scenario #1-03: Yesteryear's Truth PDF" being listed for this event, one on Dec 29, 2017, the other on Jan 19, 2018.
I can't find a way to delete the date, and there is no way I can see to remove the listing from the event.
I am having the same problem.
Event # 157142
Same issue here in reguards to that Scenario.
While I was able to report some events recently, I am now experiencing the same issues as before with reporting.
We have 3 sessions that need to be reported.
The Masked Ferret
|
The Masked Ferret wrote:Cannot report 2 sessions on 155317Up to 5 sessions now that cannot be reported.
Thanks, Robert, for the update about the timing. I would love to be able to get these tables properly reported.
Up to 7 sessions that need reporting. Any updates? This has been at least 2 months of not being able to report my event.
| Scott Romanowski |
It looks like I can report sessions to my event. However, since "early December" had passed and reporting was still broken, I created a new event for the store and reported the sessions there. Now I'm torn between doing the work to report them on the old number, continuing to use the new event, and deleting the new event; or continue using the new event.
The Masked Ferret
|
The Masked Ferret wrote:Up to 7 sessions that need reporting. Any updates? This has been at least 2 months of not being able to report my event.The Masked Ferret wrote:Cannot report 2 sessions on 155317Up to 5 sessions now that cannot be reported.
Thanks, Robert, for the update about the timing. I would love to be able to get these tables properly reported.
Session now reported, but Starfinder characters are not showing the Fame or sessions on their character page from the submitted events.
The Masked Ferret
|
The Masked Ferret wrote:Session now reported, but Starfinder characters are not showing the Fame or sessions on their character page from the submitted events.Thanks for bringing this to our attention! We have diagnosed this problem and are in the process of fixing it.
Thank you so much!