• State Verified Answer
  • Date
    fohlwilting
  • Date
  • Replies 19 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 3854 views
  • Users 0 members are here
Options
Related

Support request regarding Fixture Library Hub

Hey there,

it seems like I suddenly can't add a request in the Fixture Library Hub. I already used it a few times for Hog v4 fixture requests. Now it is the only way to request fixtures for EOS. I wanted to add a change request for Cameo AuroSpot CLAS200. I already tried it a few times. I entered the following information.
I'm logged in so it does not ask for name and email. Platform "Eos v3" is chosen. Manufacturer "Cameo", Fixture Name "Auro Spot CLAS200", Personality / Mode "13ch", DMX Footprint "13", Documentation: I uploaded a document named "Cameo Auro Spot 100_200.pdf" (2.29MB). I didn't check private, selected 21th of october 2023 as need by date. First date enabled to be chosen is the 15th. I commented the following:

Hey,
DMX documentation is on page 41 and 42.
I'd like there to be a "Beam FX Mode" like there is a "Gobo Mode".
The issue is that Rot+ and Rot- do not use the same user range.
I can't toggle between forward and backwards rotation with same speed
like it is possible with gobo rotation. I suggest adding a
"Beam FX Mode" with Index, Rot+, Rot- and in "Beam FX Index/Speed" in
Mode "When Beam FX Select is effect 1" there should be three corresponding
modes with equal user ranges. Thanks a lot!
Lars

I of course checked the reCAPTCHA.

When trying to submit it keeps loading. As I said I already tried a few times. Can anyone identify the problem?

Another little side comment: When visiting "Your Submissions" > "Requests" in my account view, I can't identify the platform of each of that fixture requests:

Thanks a lot everyone!

Greetings from Germany

Lars

Parents Reply Children
  • 0 in reply to fohlwilting

    Hello Lars,

    I pushed out an update to the Hub. Can you please try logging in again and submitting a request?

    -PH

  • 0 in reply to patrick hutchinson

    Sadly still does not work. But I had a look at the console and there are two errors:

    POST https://fixture-library-hub-api.etcconnect.com/api/request
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://fixture-library-hub-api.etcconnect.com/api/request. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 500.

    Translated:

    POST https://fixture-library-hub-api.etcconnect.com/api/request
Cross-source (cross-origin) request blocked: The same-source rule prohibits reading the external resource at https://fixture-library-hub-api.etcconnect.com/api/request. (Reason: CORS header 'Access-Control-Allow-Origin' is missing). Status code: 500.

    Seems like a missing argument in the post request header?

  • 0 in reply to patrick hutchinson

    By the way I get the same error using Chrome:

    Access to fetch at 'https://fixture-library-hub-api.etcconnect.com/api/request' from origin 'https://fixture-library-hub.etcconnect.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
RequestPage.js:213     POST https://fixture-library-hub-api.etcconnect.com/api/request net::ERR_FAILED 500 (Internal Server Error)
(anonymous) @ RequestPage.js:213
c @ regeneratorRuntime.js:44
(anonymous) @ regeneratorRuntime.js:125
(anonymous) @ regeneratorRuntime.js:69
On @ asyncToGenerator.js:3
a @ asyncToGenerator.js:22
(anonymous) @ asyncToGenerator.js:27
(anonymous) @ asyncToGenerator.js:19
(anonymous) @ RequestPage.js:243
(anonymous) @ Formik.tsx:851
(anonymous) @ Formik.tsx:1202
(anonymous) @ Formik.tsx:758
Promise.then (async)
(anonymous) @ Formik.tsx:733
(anonymous) @ Formik.tsx:1202
(anonymous) @ Formik.tsx:825
(anonymous) @ Formik.tsx:1202
ze @ react-dom.production.min.js:52
Je @ react-dom.production.min.js:52
(anonymous) @ react-dom.production.min.js:53
jr @ react-dom.production.min.js:100
Sr @ react-dom.production.min.js:101
(anonymous) @ react-dom.production.min.js:113
Oe @ react-dom.production.min.js:292
(anonymous) @ react-dom.production.min.js:50
Tr @ react-dom.production.min.js:105
qt @ react-dom.production.min.js:75
_t @ react-dom.production.min.js:74
t.unstable_runWithPriority @ scheduler.production.min.js:18
Vo @ react-dom.production.min.js:122
Ze @ react-dom.production.min.js:292
Xt @ react-dom.production.min.js:73
RequestPage.js:241 TypeError: Failed to fetch
    at RequestPage.js:213:13
    at c (regeneratorRuntime.js:44:17)
    at Generator.<anonymous> (regeneratorRuntime.js:125:22)
    at Generator.next (regeneratorRuntime.js:69:21)
    at On (asyncToGenerator.js:3:20)
    at a (asyncToGenerator.js:22:9)
    at asyncToGenerator.js:27:7
    at new Promise (<anonymous>)
    at asyncToGenerator.js:19:12
    at RequestPage.js:243:10

  • 0 in reply to fohlwilting

    Hello Lars,

    I have been trying to reproduce your issue but am having little luck. Can you please generate a .har file from the fixture request you are trying to submit? Please use the following link for instructions on generating a .har file then attach the file once generated.

    https://help.okta.com/oag/en-us/content/topics/access-gateway/troubleshooting-with-har.htm

    Cheers,

    -PH

  • 0 in reply to patrick hutchinson

    Hey  ,

    can I send you the .har file as private message or can you share an upload link with me? Thanks

  • 0 in reply to fohlwilting

    Hello Lars,

    I just sent you an email with a link to a Cloud location you can place the .har file. Let me know if you do not receive it.

    Cheers,

    -PH

  • 0 in reply to patrick hutchinson

    I did not receive an email. Not even in spam.See no evil It seems like I can't send it to you via PM neither.

  • +1 in reply to fohlwilting

    Hello Lars,

    Thank you very much for sending over the .har file and I apologize for any frustrations this issue might have caused. With a little bit of analysis, a colleague and I have determined the issue. What we found is the comment you added to the request was flagged by our firewall as being potentially malicious. We have updated the firewall rules and I am confident that your next request submission will be successful. Can you please try submitting your request again?

    Cheers,

    -PH 

  • 0 in reply to patrick hutchinson

    Success!

    Thank you a lot! I mean it was frustrating a few times, but the joy of having the problem fixed is greater.

    Out of curiosity, can be identified which part of the comment was the problem?

    Thanks

    Lars

  • 0 in reply to fohlwilting

    Hi Lars,

    IT guy here. I'm not sure how helpful it will be, but I've included a screenshot below of the specific section that got flagged (highlighted). It seems the pattern match was along the lines of "double quote followed by space, followed by the word 'like' followed by space".

    Sorry for the hassle with this. Firewalls are very helpful, but sometimes can definitely get in the way.

    Drew

www.etcconnect.com