Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

H Games wiki

There is UploadStashBadPathException after file uploading attempt on Special:Upload page in hgames wiki. Wiki administrators, please look into this issue. Maybe the wiki ran out of disk space?
 
otteraliens said:
There is UploadStashBadPathException after file uploading attempt on Special:Upload page in hgames wiki. Wiki administrators, please look into this issue. Maybe the wiki ran out of disk space?
Click to expand...
I will take a look, but it's not the disk space for certain.
 

Attachments

  • sample0.png
    sample0.png
    225.3 KB · Views: 7
What else could it be? Did you try a VPN with a connection over a different country?
The only other difference could be between our users.
 
Last edited:
I could reproduce the problem by clicking "Browse" and then instead of selecting a local file I put the URL from Illusion.rip site from above. The result is the warning for the '[' bracket. And when I still ignore that warning, then I get the error mentioned in the OP.

1784391617101.png
 
There seems to be some silent error, not showing on the page. But that one needs to be ignored. A task for Checkmate :P
 
I have been contemplating how to manage the wiki. It's not going away, but it has always felt like a throny rose to me. The ASF v2.3 at least has an OAuth server that I can use to unify the login. However, having the wiki separate from the website makes it feel quite strange.

Thank you for maintaining it
 
Having a single user for ASF and wiki is a very good thing.

And you posted about an integration of the wiki. Not sure how the handling for users would be; they need to be able to edit one and the same post commonly. And what about the history of changes? If you want to go that way, please make a test migration first and ask the active users of the wiki how they feel about it before closing the old one.
But you are right, a wiki has its own standards. It is a different world from every forum.
 
enimaroah said:
Having a single user for ASF and wiki is a very good thing.

And you posted about an integration of the wiki. Not sure how the handling for users would be; they need to be able to edit one and the same post commonly. And what about the history of changes? If you want to go that way, please make a test migration first and ask the active users of the wiki how they feel about it before closing the old one.
But you are right, a wiki has its own standards. It is a different world from every forum.
Click to expand...
Nothing in my plan would compromise the wiki nature of the site. Since 2021, I have been evaluating and discarding ideas, but I have narrowed it down to few options:
  1. Implement a simpler wiki system integrated directly with ASF. This approach would ensure that all security and maintenance handled by ASF would cover the wiki as well. The wiki would likely inherit all the rich media formats available through ASF, including the site's responsive design, resulting in less spam. The risk is that this light version of the wiki will be less flexible than the full version of MediaWiki. However, I've been waiting and haven't seen anyone utilize the advanced features of MediaWiki, so this concern may be irrelevant. I'm uncertain if or when we will ever need those features.

  2. Launch a fully-fledged version of the wiki system, while still integrating it with ASF. This option may result in more bugs, greater complexity, and an increased likelihood of things breaking. However, it would provide the complete functionality of MediaWiki. I'm not entirely certain about the responsiveness aspect, but it would require significantly more work.

  3. Maintain the current wiki as it is, but unify user login. This option carries the least risk, but we would lose all the advanced features we should have, such as responsive design, dark theme, and an easy rich text editor. Additionally, it would not benefit from ASF's robust security and maintenance, leaving it vulnerable to spam. Development plugins and theming for mediawiki remain challenging, as public code are extremely limited, custom made module must be budget rather carefully.
 
I apologize for prying into my own business, but have you considered using wiki addons for XenForo? Maybe you can try to test them and simply transfer the wiki from the mediawiki directly to XF? The only possible downsides are probably the loss of editing history and the possible lack features.
 
otteraliens said:
I apologize for prying into my own business, but have you considered using wiki addons for XenForo? Maybe you can try to test them and simply transfer the wiki from the mediawiki directly to XF? The only possible downsides are probably the loss of editing history and the possible lack features.
Click to expand...
Yes, in fact, it was on my worksheet, there were 3 addon wiki for xenforo:

1. The Xwiki created by ThemehouseDeadware, RIp, no longer seems to care about their old customers; they're now focused on catering to larger businesses that want their own communities.

2. The XenCarta Wiki is a mini wiki system that shows a lot of promise. With some customization, it could work really well, but it has some serious limitations if we ever go beyond 100 games. It's unlikely, but you know what they say-never say never!

3. The VaultWiki, which used to be called the vBulletin Wiki, was buggy back in the day, and it still is now. I could probably fix most of the bugs and make it functional for us, but the whole system feels overly complicated with its strange and confusing folder structure.

But whatever system we move to, everything should be ported as much as possible, that include the editting history, or it won't be a plan
 
No extra work or complexity for the staff, and especially not if the additional features are not used anyway.

I would vote for option #1, but it depends on how much simpler this wiki will be. My experience with media wiki is small, and zero for others. So, I would like to see and try the simple one you choose for ASF with a few pages migrated for testing.

Old links? Will it be possible to maintain old links and forward into the simple wiki? It might not be critical if not, but would be nice to have.
 
Checkmate said:
  1. Maintain the current wiki as it is, but unify user login. This option carries the least risk, but we would lose all the advanced features we should have, such as responsive design, dark theme, and an easy rich text editor. Additionally, it would not benefit from ASF's robust security and maintenance, leaving it vulnerable to spam. Development plugins and theming for mediawiki remain challenging, as public code are extremely limited, custom made module must be budget rather carefully.
Click to expand...

Regarding responsive design, I'd like to add that responsive design kills the wiki's flexibility. You simply can't insert your own HTML markup without worrying about it being moved around by responsive design. Custom color schemes are a similar problem. Therefore, I suggest considering whether these features are necessary. In particular, how many users are accessing the wiki on smartphones? Are there any articles about mobile games at all (I personally don't see such a section on the main page)?
 
You must log in or register to reply here.
Top Bottom
Back