Jump to content

trq

Staff Alumni
  • Posts

    30,999
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by trq

  1. You have got to be kidding. http://www.w3fools.com
  2. With that in mind though, be aware that the singleton pattern is often referred to as an anti pattern. It should really be avoided unless you understand why. Lines like this: $db = Database::getInstance(); within another class are a good example of why a singleton is bad news. It has tightly coupled your class with some Database class that it is expecting to always exist within the global namespace.
  3. Why, what do you hope to achieve by doing so?
  4. Why are you even attempting to do this? It does nothing but annoy users.
  5. Not likely. If system has been disabled, the other similar functions have likely also been disabled.
  6. Thats not how this works. How about you tell us specifically what your issue is. And we'll see if we can help.
  7. Your post indicates that you are under the impression that code was written by us? Its not. I would suggest you take your request up with the developer of the code in question: https://github.com/deepeshmalviya
  8. Its harder to edit and debug for one. Most people decide to use the right tools for the job, that includes editors capable of handling html well. Storing your markup in a database removes these tools from the equation. Besides, I really don't see any need to store anything but the most simple markup in a database. Markup is part of your application, not part of your data.
  9. Yeah, well its not really something I think you'll implement all that cleanly so... I'm not sure its the best design decision. I mean, markup in the database, just seems very dirty to me.
  10. Still, markup in the database smells bad, but anyway.... It sounds more to me like you need to add classes to your markup, and then create a means to generate your css dynamically. Its a much simpler solution that results in the same sort of end result. It should be pretty simple to create an interface to edit css.
  11. Why are you storing your markup in the database in the first place?
  12. We are not here to write code for people, the manual is full of examples. What have you tried? Be specific.
  13. Anyone working with Rest API's needs to install postman: https://chrome.google.com/webstore/detail/postman-rest-client/fdmmgilgnpjigdojojpjoooidkmcomcm?hl=en
  14. I fail to see whats rude about my reply, telling people how it is isn't rude. 30000+ posts on this board, and I have not once asked for, nor received any form of monetary payments. Now go ahead and block / ban my account! Why? You have done nothing wrong. Now... can we please stop bumping old threads?
  15. Obviously the tutorial didn't really explain anything well then? Your not likely to get help without a specific question / problem.
  16. I removed your original thread because it was an unformatted blob of text with no question attached. I'm locking this one for the same reason. The error tells you specifically where the problem is, I suggest you either fix it, or narrow it down some before dumping code here. ps: We have [ code ][ / code ] tags here for formatting code so that it is readable, please use them.
  17. This has been done a thousand times over, no need to reinvent the wheel. https://github.com/machuga/authority
  18. Store the information you need to restore the current sort state somewhere when it changes.
  19. Your going to need to explain what your actually doing here as this statement doesn't make a whole lot of sense.
  20. The last three replies have been useless and completely off topic. Thanks. Closing in case more appear.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.