• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

"Expression hasCodeBlock" exception after upgrade from 2.1.7b3 to 2.1.8

 
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've just upgrade JForum 2.1.7b3 to 2.1.8 using java 1.5 in tomcat 5.5. We create a custom war (via maven2) by overlaying a slightly modified version of the default template header.htm, style.css, and a couple of images. This along with our settings in SystemGlobals.properties is the only differences from the standard distribution. This overlay worked fine with 2.1.7b3. After upgrading to the 2.1.8 war version, we've run into the following problem.

After the upgrade I get the following exception from the main forum index:



The appropriate page is shown in the result on top followed by the exception above followed by what appears to be the error page. It shows in a "Information" box the following:

An error has occurred.

For detailed error information, please see the HTML source code, and contact the forum Administrator.

Expression hasCodeBlock is undefined on line 16, column 6 in default/bottom.htm.




Searching the community shows little to indicate what the source of the problem is.

In help is greatly appreciated.

Thanks,
Skip
[originally posted on jforum.net by skipwalker]
 
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Aw shucks. Nevermind. I went back and did another dif between my header.htm modified from 2.1.7b3 and the new 2.1.8 header.htm. Looks like I missed merging some pieces from the file. I think updating that file should take care of this issue at least.
[originally posted on jforum.net by skipwalker]
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!