What the heck is that code doing?
REMEMBER : Before you reduce the differences, make sure that you back up your override files to another location on your computer.
If you are like me, you find code pretty baffling. Quite often, when WebWorks introduces new code, I have no idea what it is doing. To get around this, I break down my process. It takes a bit of time, but it is worth it in the end.
CAUTION : This approach usually works for me. However, code in one override file might depend on code in another override file. In which case, adding new code incrementally might prevent your output from generating properly.
1. Reduce the code differences that you understand.
2. Make sure that you can still generate your output in ePublisher as expected.
3. Back up your override files again.
4. Return to the files that have new code.
5. Add the new code to your override file, and then regenerate your project in ePublisher.
6. If the project does not create output as expected, then copy your backup override files back into your override folders so that you can start adding the new code all over again.
7. Add the new code in increments.
For example, make the changes one file at a time. Or if there is a defined section within the file, then make the changes in that section.
8. Regenerate your project in ePublisher.
9. Continue to regenerate your project and add new code until all of the new code is added to your override files and your output generates as expected.
Published date: 10-17-2023
Last modified date: 09-28-2023