Help publishing a new mod to SMF customization

[prdx]

Hi all. I'm sorry if this is a recurring question — I've searched this board but couldn't find a similar case.

I'm new here. I've been managing a forum for many years, but always just as an admin. Now I'm also maintaining the whole stack.

I come from a sysadmin background (I'm a professional sysadmin/SRE) and have some experience with coding — though PHP is quite new to me, and I'm slowly learning.

I've made a few mods for my forum, and some might be good enough to share. I was trying to submit a simple one that embeds Twitter/X posts into topic messages.

I've carefully read the GitHub integration topic to check if I missed something, but I believe I'm meeting all the requirements:
- The GitHub repo has a tagged release and an uploaded artifact.
- It contains only one mod, located at the top level.
- The package installs successfully on my forum and works as expected.
- I'm using the repo URL without a trailing slash.

However, I get an HTTP 500 error when submitting it, so I'm unable to see what needs fixing.

As far as I can tell, everything is in place: there's a license, a README, and a well-formed package-info.xml with all the required metadata.

Are there checks — like whether the zip filename must match something specific — that I might be missing?

Any help would be much appreciated!

[shawnb61]

Where are you seeing the http 500?

[prdx]

- I go to .../index.php?action=post;type=mod
- New mod
- From a GitHub repository -> Continue
- Select all information:
  * New Feature
  * Tried leaving Tags blank or put something
  * GitHub repository link: https://github.com/smf-prdx/smf-mod-xpost [nofollow] (I guess it will be disabled because I'm new)
  * I choose two screenshots and SAVE

And crashes with 500 HTTP error. Screenshot included.

[shawnb61]

Ah...  That looks like an issue with the customization site.

[prdx]

Good to know! I was mad trying to figure out if it was just me.

I guess this is the right place to report the issue, isn't it?

[shawnb61]

Yep, "Site Comments, Issues and Concerns".

[Sesquipedalian]

@SleePy will probably come by soon and fix it.

[SleePy]

Composer update failed on me.  Should be good to go.

[prdx]

Thanks a lot for your feedback. Sadly it still complains with a 500.

Probably I'm doing something wrong 

[SleePy]

Nope, it's on our side.  I think I got it squashed this time.  A composer library changed its namespace, causing a failure to find the library.  Only affecting new customizations, so a bit tricky to verify on production, but works in my dev env.

[prdx]

Finally got it sorted — huge thanks for the help, SleePy!