When I run any model unit tests, are they supposed to run the model_installer.php up to the latest version inside that .php file? Mine seem to ignore any up_x(). Perhaps it's time for a fresh install. Thanks.
Do you have the a test/fixtures/app/installers/model_installer.php file with this code on it?
<?php require_once(AK_BASE_DIR.DS.'app'.DS.'installers'.DS.substr(strrchr(__FILE__, DS), 1)); ?>
Yup, it has that exact line.
Also, the file inside /test/tmp/installer_versions/testing_spotstransfers_version.txt has the number 1. (I have 'function up_5()' inside the real spots_transfers_installer.php).
./script/test model SpotsTransfers
Works, but has the issue described above. It thinks that the latest revision in development is version 1, when in reality I'm at version 5. The testing database reflects version 1 as well. Any suggestions? {edit} It appears that no matter what model I try, it only installs revision one in the testing database. Hml! {/edit}
Ok, here's another strange thing. I do "svn update", but now my ./scripts/ have <<<<<<<< and >>>>>>>>> in them. I want only the latest version, not some .mine and some .r435 or whatever. Obviously the <<<<<<<<< >>>>>>>>> make the ./script commands fail.
Answer: Do a svn revert and update like such:
svn revert -R /path/to/akelos
svn update /path/to/akelos
Hello,
This is quite easy. Those chars are from a subversion merge conflict. It seems you have some local changes in your file that are incompatible with the changes from the main repository. If you don't need that changes anymore you can do a "svn revert filename" to get the most current version from the repository. If you still need your own changes to that file. you have to edit the file (merge the file by hand). After that you have to resolve the conflict such that subversion knows you have solved that conflict. This is done by issuing the command "svn resolved filename".
Hope this helps.
Thanks for your help! I don't remember making any changes to those script files. Oh well.
1 to 6 of 6