Extiverse. Breaching the frontier in Flarum forum and community management

GreXXL

I have made two observations - both non-critical - but wanted to mention still 🙂

If you purchase an extension and get redirected back to extiverse after payment you land on the subscription page. The only downside the newly purchased extension is not shown - only after a page refresh 🤐

The login/sign up is really badly visible especially on mobile (like iPad). It should be moved directly under the extiverse logo in the sidebar and not at the very bottom.

luceos

Darkle will look at this as soon as I can. Sorry that this happens, must be frustrating.

GreXXL If you purchase an extension and get redirected back to extiverse after payment you land on the subscription page. The only downside the newly purchased extension is not shown - only after a page refresh

You should be redirected to the page that lists your active subscriptions, not the available subscriptions of the extension. Will look at that.

GreXXL The login/sign up is really badly visible especially on mobile (like iPad). It should be moved directly under the extiverse logo in the sidebar and not at the very bottom.

Okay. A redesign is planned, just not sure when I have the time or money to do that. Extiverse hasn't even surpassed break even yet.

GreXXL

luceos You should be redirected to the page that lists your active subscriptions, not the available subscriptions of the extension. Will look at that.

I think you are redirected to your subscriptions, it just doesn't show the newly added one without refreshing 🙂

luceos Okay. A redesign is planned, just not sure when I have the time or money to do that. Extiverse hasn't even surpassed break even yet.

Do an Collective, I'm in?

Darkle

luceos will look at this as soon as I can. Sorry that this happens, must be frustrating.

About this I wanted to clarify, a few days ago I completely cleaned my browser and the error has not happened again.

So it was from my side, but maybe caused by this, when the problem started was the same day I deleted lots of "composer" tokens that I had been creating over time and by mistake I also deleted the "app" token, maybe this caused it and there is a bug that doesn't allow to restore the "app" token after deleting it (?)

luceos

Extiverse is hitting the api limit with github, which requires a refactor on my end using conditional requests (https://docs.github.com/en/rest/overview/resources-in-the-rest-api#conditional-requests). I will try to get this done as soon as I can.

The rate limiting causes extension updates to become available less quickly. Mercury and the helper are also impacted as they both rely on the accuracy of the extiverse database, which will probably lag behind a bit.

luceos

Darkle that should not happen. If the app token no longer exists you should gain a new one automatically. Maybe I need to disallow deletion of that token 🤔

pupsik

luceos probably doesent matter, but mobile view is a bit off.

Mark73

For some reason, Extiverse is only showing premium extensions

luceos

Mark73 thanks Mark, extiverse is recovering 👍️

rafaucau

@luceos When I run composer update, I get this error:

                                                                                                                                                                                                                                                                                                    
  [RuntimeException]                                                                                                                                                                                                                                                                                
  Could not load packages kilowhat/flarum-ext-wordpress in composer repo (https://extiverse.com/composer) from root file (https://extiverse.com/composer/packages.json): [UnexpectedValueException] Could not parse version constraint ^>=0.1.0-beta.13: Invalid version string "^>=0.1.0-beta.13"  
                                                                                                                                                                                                                                                                                                    

                                                                                                  
  [UnexpectedValueException]                                                                      
  Could not parse version constraint ^>=0.1.0-beta.13: Invalid version string "^>=0.1.0-beta.13"

I don't even have this extension, so it's probably a problem with Extiverse

luceos

rafaucau I'm looking into that.

luceos

Okay after some extended research I discovered the cause coming from an incorrect flarum/core dependencies. I've resolved this with the author of the extension and finally found a way to prevent this from happening again.

luceos

@iPurpl3x reported that all non-premium extensions aren't indexed. I'm looking into it.

Edit A database problem caused the sync to fail. The sync was restarted not too long ago and the extension index has been restored.

1Dot

Hello @luceos Sir Exitverse is returning 500 Internal Server Error on searching.

Mark73

1Dot I can't relate. It's working fine for me.

1Dot

Mark73 Yeah now it's working! Before it was returning 500 error

luceos

Extiverse is currently listing only premium extensions. It has had issues the past few weeks with errors during searches which I resolved this week. This instability with extiverse is not something I'm proud of, but I have lacked the time to look into it. Right now I'm also not behind a PC to reinstate the index to include the open source extensions.

My apologies for this hickup. I'm hoping to fix the index somewhere this weekend. Next week I'll look into the stability issues again.

Juba007

It looks like Extiverse is down.

luceos

Juba007 yeah monitoring just let me know the same thing and I confirmed an empty resultset. Before I could investigate it was back online. I will be looking deeper at things the coming weeks, because something has become extremely unstable in this stack.

luceos

So right now there are three issues that I know of with high priority:

Occasionally all open source extensions are missing.
Sometimes the index throws a 500 error.
Searching throws a 500 error.

The coming days I'll be looking at all of these. But just so you know that I am aware about the problems with Extiverse.

Edit: search fixed.

« Previous Page Next Page »