Help upgrading from 1.5.7 to 2.0

Ive tried the updater in the system and it errored due to a missing file. one i found and added the file the site came back up but showed that i was on the same version. Here is the error for reference

coldfusion.tagext.lang.IncludeTag$NoSuchIncludeTemplateException: Could not find the included template templates/bootstrap-adminMenu.cfm.
	at coldfusion.tagext.lang.IncludeTag.setTemplate(IncludeTag.java:347)

I tried to manually update to the 1.6 version but the archive download on the site is not accessible.

not sure what else to do

What is the URL of the archive you’re trying to download?

What if you restore from a backup and try again?

Thanks!

~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

http://www.gocontentbox.org/parent/site/download?version=1.6.0

Yep, looks like Luis moved that download into an archive folder and forgot to update the download link on the site. Try here instead:

http://downloads.ortussolutions.com/ortussolutions/contentbox/archive/contentbox_1.5.7.zip

Thanks!

~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

So i tried scrapping everything and starting fresh since i only had a few posts, i backed up the db. I downloaded ContentBox 2.0 and uploaded it to my hostek server and now when i hit the homepage to go through the setup it tries finding “/modules/contentbox-dsncreator” and gets stuck in a redirect loop. I checked and the folder exist not sure what the issue is.

Common issues that can cause either 404 or redirect issues are:

  • IIS connectors need to be reinstalled
  • URL rewrites aren’t configured
  • Trying to run the app in a subdirectory that includes the word “contentbox”
  • Running in a subdirectory while using a servlet container that doesn’t allow double-wildcard servlet mappings (Anything OTHER than JRun and the modified version of Tomcat that ships with ColdFusion)

See this ticket CONTENTBOX-363

Here’s also some forum threads for similar issues:

https://groups.google.com/d/topic/contentbox/BftO1InK5CQ/discussion
https://groups.google.com/d/topic/contentbox/0JJeb0LvfiI/discussion

Thanks!

~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

I got past the problem of the redirect by renaming the .htaccess. when i loaded up the site it let me do the database wizard, but when it redirected back to the home page it gave me the error:

10/23 12:29:01 Error [jrpp-7497] - Table cb_menuItem defined for cfc contentbox.model.menu.item.MediaMenuItem does not exist. The specific sequence of files included or processed is: D:\home\aresdev.com\wwwroot\index.cfm’’

I double checked to make sure that the datasource could create tables so im not sure what the problem is.

I’m going to try again one more time. Could you point me in the direction of the most updated version so i can have the best chance of getting up and running.

I think you officially might have server gremlins. I swear sometimes it seems like ContentBox either works flawlessly, or invents new error messages.

Are you wanting to just install the newest version fresh? Make sure you start with an empty database, fresh copy of the code (running the installer modifies certain parts of the code) and restart the server to clear our application scopes.

The download from our main download page should be the current stable version.

Thanks!

~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

Ok i think i got the Gremlins out lol. I used the version “master” from github and aside from a few issues that i encountered it is now up and running. I experienced the issue with localization since I’m on CF 9 when using the variable “default” so i renamed that and we were ok. And then the other was related to the “woff” file type not being added in the .htaccess under valid file types so once those were fixed its running smooth. :slight_smile: