[SOLVED] Catalogue Issue
#5660 (In Topic #1319)
1) When trying new things and a solution has been found, be VERY sure to undo everything else that was done to get to that point (also make sure those steps/attempts are recorded somewhere lol) and not related to the end result.
2) Tinkering as a troubleshooting methodology is generally not a good idea. Head back to the original starting point and build your way back up.
Oh well, on the upside: troubleshooting usually means poking around and trying out things that one may not have normally tried out and as a result, new stuff is learned.
Last edit: by SoccerDad
I can say that for that to be valid syntax a comma is needed:
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
I swear Chris, starting with my own damn self, commas and semicolons are next in line on my 'put me in an early grave' list! Thanx kindly for pointing that out, 'twas the issue all along!
*mutter*, damn commas, *mutter*, stoopid semicolons, *mutter*
1 guest and 0 members have just viewed this.