Read the statement by Michael Teeuw here.
How do I configure a module?
-
@ArcherProject before you know it you’ll be an old pro at this!! It does get easier hang in there and if you run into trouble just ask! :)
-
Again, you sound just like I did. I took the time to help you because a few weeks ago I was in exactly the same place as you are now and someone here stepped in and answered my questions and was very explicit in their directions. It got my MM up and running, gave me some confidence and taught me something. I still ask questions but I’m not afraid to experiment beforehand.
Another piece of advice:
Make a copy of any files you are going to edit (e.g. your config file, your css files, etc…) and work on those. If you mess anything up, you go back to the original. In my config folder I have my working config.js file and I have backups named configV2.js, configV3.js, configV4.js (etc) for each time I edited the config.js file. More than a few times I messed up something but I had the backups as a safety net. I trash the one I messed up and renamed the last working backup to config.js and continued the process.
-
@Mykle1 Oh good lord… I can’t count how many I messed up LOL
-
@cowboysdude My point exactly
-
@ArcherProject said in How do I configure a module?:
@Mykle1 thanks miate exactly what I have ended up doing and now I’m feeling a lot more confident! attempting to add a few extra modules too and so far so good! hope to make another one of these for myself in the future (this one is a gift). feel like I’ve still got a lot to learn though!
HEY do yourself a HUGE favor… when you have a working config.js just copy it to config.bak for a backup!! That way you can always look at it and see perhaps where you went wrong… trust me it’s a HUGE time saver!! :)
