Jump to content
MakeWebGames

a_bertrand

Members
  • Posts

    3,655
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by a_bertrand

  1. Chainging too much of an engine could lead to future incompatibilities for the person doing it so, for example if you rename the directory modules with "mod" any modules relying in the previous structure will break and you will need to edit them by hand. As I saw gmoore is thinking of (or already did?) change all admin modules directories and added an index.php file on each mod, I was wondering how I could try to help him in some manner. My proposal would be that during the installation of the module, the directory of the module would be made somehow unique, like instead of admin_panel you would have admin_panel_56ae where the last 4 numbers are like a CRC of your license + the module name. With such change each game install (with a different serial that's it) would have different modules directories. That would have quiet some impact on the current code, and modules, but could be still done (as option) if you guys think it's of some value. Of course we could also add a default index.php files on each directory as well if you wish so :P Let me know what you think.
  2. You need to click the "Set on sale" button, once you have the module on the screen. This is like a "pre-publish" state to allow you to edit the details.
  3. Always, such that I can do more in my day ;)
  4. Chat rooms are indeed useful, as well as private chat would be great. However I wonder if it doesn't make sense you go for an IRC chat or something like that if you need all that features. Blinking => unless you do it in JS most browser stop accepting / supporting it if I remember right. Anyhow I will keep all those as wishes, and see if I manage to put them in.
  5. Just accepted the module yet.
  6. I doubt I ever ignored on purpose any security hole, whatever was reported as security issue (like the NPC discussion) has been addressed. Maybe on some form, that's due to my own twisted way to solve things, but yet I hope to follow any feedback I ever had. The only thing which I didn't addressed yet and I remember you reported to me Octarine is the need of unit testing. Something else I forget? For the index.php file on each directory, honestly I doubt it adds much security as well as I doubt changing all files in php does and good. Why? First of all the .htaccess should prevent to browse the files, second the modules files called directly do... nothing as they lack all the lib files. So I hardly see adding an index.php file being a strong security. Anyhow feel free to do it the way you want, it's your installation anyhow ;) I don't like much the security by hiding, I think it gives a false protection feeling, where if you design the things to be safe and yet visible to all it should actually be better. Again my feeling.
  7. I see, so your concern is that if for example somebody use a 4 column design the hooks will fails and present a 2 column design. Now I starts to understand. I will look into it.
  8. Indeed I wasn't thinking of limiting the number of sites / domain YOU could use with one license. I would have left to the owner of the site to decide if to buy one license for all or one for each. Yet I don't want that somebody buy once license and redistribute it to 100 other people. So for me it would be 1 license per user, where the user is either an individual or a team working on a common project (however in that case the people of the team should not have the right to re-use the license for than that particular project). I don't know if my idea is somewhat clear. That was also the reason why I was showing the email / name of the person which bought it, and not an IP or a domain.
  9. But what would be the advantage?
  10. I have stored the IP on the server side, however ideally it should be linked to a domain.
  11. That's what I would consider the base or nearly, however some pieces could be modified like the home / welcome [TABLE=width: 100%] [TR] [TD]Core tables: users, bad_trials user_roles roles user_stats user_stat_types user_variables variables modules object_types object_types_attributes objects object_attributes inventory slots slot_type_accepted equiped module_config_values [/TD] [TD]Core modules: admin_edit_config admin_edit_tables admin_import_package admin_module_manager admin_panel admin_side_panel change_password home inside_menu login logout public_menu recover_password register security_token stats welcome [/TD] [/TR] [/TABLE] + 1 template ;)
  12. The system was thought / planned exactly as 1331 is describing it. Basically the side menu you currently have is just one of the possible menu (and actually the admin panel is using again the same structure too). You could just create a new module which runs with a different hook and fill a right or top or bottom or middle or whatever menu ;)
  13. Module accepted. It could well be that some hooks are missing in the wiki page. I simply have an hard time to fill it, too much to do, to little time.
  14. Beside the email is displayed as image and not as text (harder to harvest), I agree, it could lead to some privacy problems. Therefore I removed the display of the email.
  15. Well, that need to be thought, my idea was that you could therefore do more by echoing or doing other actions than simply adding values into an array.
  16. Could be done. I miss an ASP.NET feature here, which would allow to have reusable components for the rendering of data but I may either code it multiple times, or create yet more template functions I shall see.
  17. Yes it's close enough. You lack some stuff like the security and the caching (which could be skipped), and other you may not want in this form but it's nearly the core.
  18. For the different types of objects?
  19. You could check the free version as it's nearly the core. However I will check and give you back a better list tomorrow.
  20. I will look into those for the next release. I want also to have some "new posts" link to see what's new since your last check.
  21. would it be possible to have the forums so STAFF can >> 1 pin/unpin posts 2 move posts to other topics (example) send a whole topic to a category called PIT 3 user side which shows how many posts a user has made
  22. Ok implemented for the next release. You can call a stop refresh function which will stop the timer. Seems to work well in my trials. I will send you an email containing the files to change if you want to test it.
  23. Well you got me first while I was on holidays, so you had a delay you should not get from me usually ;) Now I'm back operational and can offer what a good service is in my opinion (or at least try to).
  24. What I would believe is that it should show the "update" even after you actually updated till you actually reload the page again. This was due to the fact I was loading the current versions before making the update and therefore it would miss the refreshed version. I hope my explanation makes sense.
×
×
  • Create New...