AbbyTan:
Dear mc,
I am confused and discouraged by whatever you said to me.
Removing the log files has NOT helped my problem at all, it remains there.
I don;t understand what you mean here "When/if posting please select the # button in the messagebox menu toolbar just before pasting the contents. This will provide code tags and make reviewing the content easier after posting." Can you tell me where to find this?
By the stage of the work, it is a lot of time wasted to choose another template. Not sure if the developer of the theme will be able to help, the last time I wrote them to ask some question, they said they don't provide service anymore for this theme.
Does it mean therefore there is no one I can turn to for help?
Please advise me, thank you
Correct, there has been some form of msunderstanding.
Now that the issue has been identified as template related, like most problems there are two paths that can be taken either fix it or replace it. Each has it's issues, but let's address the confusion from my last message first.
When ZC experiences an error that is withing it's ability to report, it generates a myDbeug log. In your version of ZC (1.5.1 and above) the log is appropriately placed in. The logs folder by default.That log fle contans information that can guide someone to identify where in the 1000's of files needed to run ZC the issue is/begins. This/these files must be reviewed (evaluated) in order to see quickly what exactly is wrong in the code. The good/bad thing about the log files is that sometimes it can provide too much information. For example if the debug file is like myDebug-adm then it more than likely contains the name of your secret admin directory which in the name of security shouldn't be published if possible.
So, the part about wrapping posted content in code tags, I still haven't figured out how to write both of them in a posted message so that they don't do their job, but... When you press reply, or reply with quote, you get a text box in which you can write a response, correct? At the top of the writing area, you should have a row of text like options such as a big B (bold) an I that is slightly slanted (italics), a big U (underline), and several other buttons. On the rght side of that list of buttons is one that looks like a hashtag or a pound sign # (depending on how you "grew up" calling it). When that button is pressed the editor gets populated with text that starts like: [CODE]. This is the opening to a code tag. Everything placed between the opening and closing version of that tag is specially formatted for reading in the forum including keeping everything that was originally in one line in one line rather than wrapping it. Anyways the closing version of that tag places a / between the [ and the C with everything else the same. It is a lot like using say a div tag or a link/href tag, or any other html markup used on a website.
So, hopefully there is some more understanding. Only need to ask to get clarificatioon(s).
In the end (summary):
- recreate the "error".
- Read/review/evaluate (do not just delete) the error logs. If do not understand the contents:
2a. Safely post the contents of the debug log(s) in a format that keeps them understood.
2b. Await response from those of the community that are offering their help freely or seek out compensation.
- Make changes to the template files to stop the errors and maintain functionality or use a completely different set of template files. By stopping the errors mean to correct the error that is iniitiating the logs not to do something to just stop the logs from being stored or something. (Trust me there have been some that have misunderstood the drection/intent and say deleted their logs directory. There the logs are no longer generated but the problem still existed...)
Help any?
