This forum is in READ-ONLY mode.
You can look around, but if you want to ask a new question, please use the new forum.
Home » support » Installation and setup » Upgrading from v0.7.929 to v1.0 and beyond...
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71863 is a reply to message #71702 ] Mon, 09 February 2009 12:40 Go to previous messageGo to next message
kevin.barsotti  is currently offline kevin.barsotti
Messages: 87
Registered: July 2008
Member
Alright, I had a busy weekend but am back on this task. I am going to do the table schema alteration/rebuild and look into getting a copy of the 0.7.x (0.7.9 ideally) framework to run comparisons on.

Regarding the availability of the old framework as a tarball, the original developers who implemented the system left literally nothing for me to work with in terms of source code or documentation. Everything I know about how the system was set up initially, and changed subsequently, is the result of forensics!

I can't even express how frustrating it is. I'm hoping that once this all is taken care of, the system will be "clean" enough that normal update activities will work without special actions or hand-revisions of necessary configuration files, so that I can keep it up to date painlessly.

I'll update this thread as test the above two options.
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71864 is a reply to message #70836 ] Mon, 09 February 2009 12:54 Go to previous messageGo to next message
kevin.barsotti  is currently offline kevin.barsotti
Messages: 87
Registered: July 2008
Member
Okay, could use a hand with this: I've accessed the repository at

http://svn.symfony-project.com

But there seem to be upwards of 15,000 revisions to page through and the associated messages don't really tell me what version a given revision contains. Can you recommend a method to isolate the revision that I'm looking for? Am I doing it wrong?

My use of SVN in the past has been largely based on instructions provided to me by those more familiar with the application. While I know enough to page back through a revision history looking for a particular trunk revision to branch off of, locating a 0.7 build of the framework in 15K entries is... scary.
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71884 is a reply to message #70836 ] Mon, 09 February 2009 16:37 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
I was planning to put the revision number in this thread, and even did a search for you on google, but came up with nothing. I don't think it was tagged in svn, which would have made it obvious. I suggest you pop the question on the developers' mailing list - I am sure Fabien and co will know the answer.


Remember Palestine
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71885 is a reply to message #70836 ] Mon, 09 February 2009 16:38 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
Addendum: the tags are not just for stable versions, as there are several beta versions amongst them. But 0.7.x was released as a beta (or so I thought) and there are no tags for that:

http://svn.symfony-project.com/tags/


Remember Palestine
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71899 is a reply to message #71885 ] Mon, 09 February 2009 17:14 Go to previous messageGo to next message
kevin.barsotti  is currently offline kevin.barsotti
Messages: 87
Registered: July 2008
Member
Yeah, I went through the same info and came up with the same lack of results. I've put a message up on the developer mailing list via googlegroups; hopefully that bears fruit.
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71909 is a reply to message #70836 ] Mon, 09 February 2009 17:57 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
I'm sure it will. Keep going - you're nearly there Very Happy


Remember Palestine
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71939 is a reply to message #71702 ] Mon, 09 February 2009 20:53 Go to previous messageGo to next message
kevin.barsotti  is currently offline kevin.barsotti
Messages: 87
Registered: July 2008
Member
Alright, I've got good news, bad news, and ugly news.

The Good: Updating the 'Id' text for that table, in schema.xml, to 'id' and rebuilding the model, plus clearing the cache, seems to have worked. No more propel exception! Yay! However, I did not know this at first because of The Bad.

The Bad: Upon doing this rebuild, the class not found error reasserted itself, forcing me to manually update config_autoload_yml.php again as per the earlier issue. With this corrected I was able to see The Good, which is to say, the module loading error-free.

The Ugly: I talked to Fabien and he informed me that the version-designation convention they used was x.y.svn_revision (i.e. 9.22.70340 would refer to version 9.22 on the 70340th overall SVN reivison). The 0.7 versions were never "good" so to speak, and were all the result of retrieving code directly from the trunk, which was in flux at the time.

Moreover, the revisions that totalled the 0.7 version spanned 1881 to 1931. What this means is that while 0.7.1881, or anything along those lines up to 0.7.1931 are valid.... 0.7.929 is an impossible combination of version and revision number. So I'm working with a version of Symfony that never existed.

The Uglier: I downloaded r1881 and compared the trunk to the base (pre-upgrade backup) code for the application. There's a lot that's different. Virtually every file. What files, in particular, should I look at more closely? Some of the differences are just version/build numbers, but some are actual software logic.
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71953 is a reply to message #70836 ] Tue, 10 February 2009 00:58 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
In my view, there are two routes you could take:

1. Grab the latest version in the 0.7.x range and download that. Snapping it in will be easy - just delete your existing /lib/symfony and /data/symfony folders and switch the new ones in. In theory this will be compatible with what you have, since any new functionality would have bumped the major version number.

2. Moving your actions, templates, layouts, model files, static classes and schema to a brand new 1.0.x project, and rebuilding it manually. This may not be as bad as it sounds, depending of course on the size of the app.

Also, if your code is not too sensitive, put your existing tarball on the web, email me a link (see my profile) and I will take a look to see if there is something obviously wrong.


Remember Palestine
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #71955 is a reply to message #70836 ] Tue, 10 February 2009 01:00 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
Btw, 0.7.x versions may have been available from the trunk via svn, but I *definately* used tarballs from the symfony site when we were using this version. We weren't using svn at the time, and downloading via svn wouldn't have worked through our firewall anyway.


Remember Palestine
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #72004 is a reply to message #71953 ] Tue, 10 February 2009 13:35 Go to previous messageGo to next message
kevin.barsotti  is currently offline kevin.barsotti
Messages: 87
Registered: July 2008
Member
halfer wrote on Mon, 09 February 2009 18:58

In my view, there are two routes you could take:

1. Grab the latest version in the 0.7.x range and download that. Snapping it in will be easy - just delete your existing /lib/symfony and /data/symfony folders and switch the new ones in. In theory this will be compatible with what you have, since any new functionality would have bumped the major version number.

2. Moving your actions, templates, layouts, model files, static classes and schema to a brand new 1.0.x project, and rebuilding it manually. This may not be as bad as it sounds, depending of course on the size of the app.

Also, if your code is not too sensitive, put your existing tarball on the web, email me a link (see my profile) and I will take a look to see if there is something obviously wrong.


I most definitely would like to get this project converted over to 1.0; it's been using an obsolete/beta version of the framework and has as a consequence proved less easy to develop and support, compared to a release version. I don't know that the second option is quite necessary yet; it seems a bit extreme.

I think it's possible to debug the application, module by module, isolate the areas where things have gone awry, and correct them. For instance, last night I did something that I am kicking myself for having not thought of before, regarding the class name issue.

The model, every time it's rebuilt, can't find this 'itemListBuilder' class. In fact, it is there, but it's named 'itemlistBuilder'. Why it did not occur to me to grep through the whole file structure, looking for the latter name, is beyond me. I did it, though, and I think I isolated and corrected the issue.

It turns out that, within /lib/model/map/itemListBuilder.php, the class name and various variables used to track its name used 'itemListBuilder' and 'itemlistBuilder' interchangeably, and the class name issue shows us the names are most certainly NOT interchangeable.

I changed all references to 'itemlistBuilder' over to the correct spelling. After rebuilding the model, it all works still (previously, I had to manually fix the capitalization in a few files every time I rebuilt). I think that problem's been torn out by the root.

I'm going to do more testing now; I'll report back with issues that I can't puzzle out completely. Progress is being made!
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #72013 is a reply to message #70836 ] Tue, 10 February 2009 14:54 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
I am somewhat embarrassed to raise it, Kevin, but after all the help I've given on this thread, you've hardly thanked me at all. I don't volunteer here for praise, but nevertheless a little demonstration of appreciation goes a long way.


Remember Palestine
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #72034 is a reply to message #72013 ] Tue, 10 February 2009 17:43 Go to previous messageGo to next message
kevin.barsotti  is currently offline kevin.barsotti
Messages: 87
Registered: July 2008
Member
I apologize; it was not my intent to appear ungrateful. Without your timely and effective assistance, the progress that's been made with this upgrade would have been possible, nor would the cache permission issue been resolved so painlessly.

I'd also understand a lot less about Symfony now than I do. You've definitely got my thanks. I even tried to take up your example and help some other people with the problems in their threads, though I haven't found many issues I feel I can help with, just yet!
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #72086 is a reply to message #70836 ] Wed, 11 February 2009 10:28 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
Thanks Kevin. Yes, by all means do assist, but don't run before you can walk. See my first posts as an illustration of that Laughing


Remember Palestine
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #74860 is a reply to message #70836 ] Mon, 16 March 2009 13:33 Go to previous messageGo to next message
kevin.barsotti  is currently offline kevin.barsotti
Messages: 87
Registered: July 2008
Member
I just wanted to follow-up on this thread that the upgrade process is nearly complete; the issues I encountered throughout proved most instructive on how not to develop a Symfony application, and I've spent the past six weeks going through the whole application, module by module, adjusting and correcting what ended up being hundreds of shortcuts and questionable implementations.

Those issues which persist are now small enough in number that a few choice threads on the other support forum and a bit of research should help clear them up. I want to thank everyone, especially Halfer, who offered their knowledge and advice in this process. It's been a long, strange trip.
Re: Upgrading from v0.7.929 to v1.0 and beyond... [message #74863 is a reply to message #70836 ] Mon, 16 March 2009 13:43 Go to previous message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
You're welcome. This thread appears to be an instructive warning to website owners to ensure that their implementers are sticking to some basic MVC rules. Symfony tries to guide this via its structure, but PHP allows all sorts of naughtiness, and there's not a great deal we can do about that Rolling Eyes


Remember Palestine
Previous Topic:Could not perform XLST transformation.
Next Topic:Installation problem on win
Goto Forum:
  

powered by FUDforum - copyright ©2001-2004 FUD Forum Bulletin Board Software