4.5.0.v01 upgrade to 4.7.0.b02 issues

EricTsuei · (This post was last modified: 05-08-2020, 11:29 AM by EricTsuei.)

I am current using windows server 2008 and tactic 4.5.0.v01.
I am trying to upgrade tactic
I can upgrade to 4.7.0.a07.
but I can't upgrade to 4.7.0.b02 or 4.8.

the browser just gives me:

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

is there any changes for the SQL or apache setup after 4.7a07?

one more, I try to reinstall it,but the install.py seems have some problems.

D:\Tactic_Install\TACTIC47b02\src\install>python install.py
()
()
********************
Tactic Installation
********************
()
()
Verifying the database is installed. The default is no password if you have foll
owed the instructions to not require a password. If you see it asking for 'Passw
ord for user postgres', you should close this window and make the database not r
equire a password first (refer to our install documentation) and resume the inst
allation.
()
('\nDatabase type is: ', 'PostgresSQL')
(if this is not the database type desired,
hit Ctrl+C to cancel and see the types available with 'python install.py -h' )
()
Please enter the base path of the Tactic installation:
()
(C:/Program Files/Southpaw) ->
Traceback (most recent call last):
File "install.py", line 909, in <module>
install.execute(install_db=install_db,install_defaults=install_defaults,data
base_type=database_type, port_num=port_num )
File "install.py", line 252, in execute
self.install_to_python(install_defaults)
File "install.py", line 568, in install_to_python
tactic_base_dir = input("(%s) -> " % default_base_dir)
File "<string>", line 0

^
SyntaxError: unexpected EOF while parsing

***remkonoteboom*** · 05-08-2020, 01:33 PM

It seems that there might be an issues with the install script in line 568 when running Python2 (I am guessing you are still running Python2):

tactic_base_dir = input("(%s) -> " % default_base_dir)

The command "raw_input" was changed in Python 3 to "input", but I am not sure "input" in Python 2 seems to mean something different. From the docs, it appears that input does an "eval" on the inputted string (Python 3 does not). This seems to produce an error if the input is an empty string.

Without a code change, you could just type "None" and it should pass through.

***remkonoteboom*** · (This post was last modified: 05-08-2020, 01:40 PM by remkonoteboom.)

Also, you could just put this on top of the file:

Code:
import six

if six.PY2:

    input = raw_input

EricTsuei · 05-09-2020, 12:43 AM

seems I need to install python 3

***remkonoteboom*** · (This post was last modified: 05-09-2020, 02:48 PM by remkonoteboom.)

TACTIC 4.7 works fine with Python 2, however, this install script has a small issue with the fix described above. We'll add that to the code base.

However, that being said, the world is moving away from Python 2, so it is recommended that if you can, you should really move to Python 3.

EricTsuei · (This post was last modified: 05-11-2020, 01:21 AM by EricTsuei.)

I have already updated to py3, but can't work with 3.8, only 3.7 is working with 4.7b2, 3.8 will give an error about some clock module missing issues.

but still have some bugs in 4.7b2, but the bug won't happen in 4.5, for example, hidden row, can't define and some times can't disappear.

then I try to upgrade to 4.8, but can't work. the page can't be load. as 4.8 does not release yet, I think it might not be a problem.?

and column definition mode can't use XML to define, only form mode.

listy · 05-11-2020, 08:57 AM

(05-11-2020, 01:05 AM)EricTsuei Wrote: then I try to upgrade to 4.8, but can't work. the page can't be load. as 4.8 does not release yet, I think it might not be a problem.?

and column definition mode can't use XML to define, only form mode.

The last one is fixed in 4.8. All other bugs will be fixed soon

***remkonoteboom*** · 05-12-2020, 03:12 PM

Can copy and paste the error for this:

"error about some clock module missing issues"

We are currently running 3.7.6, so I wouldn't have seen this 3.8 error.

***remkonoteboom*** · 05-12-2020, 03:23 PM

Also, Listy is correct. We are making a push with this worldwide business slowdown to make the VFX template work well with 4.8. I am not sure I would recommend using 4.7 for VFX. We can back port some specific fixes if 4.7 is absolutely needed, but I think don't see a lot of advantages for moving to 4.7 from 4.5.

All of our efforts right now are towards making the VFX template work well with 4.8 as it provides the greatest benefit.

EricTsuei · 05-13-2020, 04:07 AM

OK, I now continue to use 4.5, and I hope 4.8 release soon.