I’m pleased to announce the first release candidate of RTFM 2.2.0.
2.2.0 is a significant overhaul to RTFM that cuts out about 50% of the
application’s code and adds new features, increased stability and more
flexibility. (Basically, we took out all the bits where RT and RTFM did
similar things and made RTFM just use RT’s bits.)
You likely need RT 3.4.3 or newer to make use of RTFM 2.2.
I’m pleased to announce the first release candidate of RTFM 2.2.0.
2.2.0 is a significant overhaul to RTFM that cuts out about 50% of the
application’s code and adds new features, increased stability and more
flexibility. (Basically, we took out all the bits where RT and RTFM did
similar things and made RTFM just use RT’s bits.)
You likely need RT 3.4.3 or newer to make use of RTFM 2.2.
I’m hoping for a 2.2.0 release sometime before Christmas.
Typical, just after I installed 2.0.4 :-/
Anyhow something you might want to consider…
‘make’ seems to install half the necessary, whereas ‘make install’ (as
documented) seems to install the rest. Might be worth noting in the
doco that ‘make’ will install a non working version.
Also the RTFM installation really had provlems - lots of ‘Unable to load
errors X from DBIx::Searchbuilder…’ errors… upgrading all the perl
modules fixed it and now it works fine…
‘make’ seems to install half the necessary, whereas ‘make install’ (as
documented) seems to install the rest. Might be worth noting in the
doco that ‘make’ will install a non working version.
Where did we suggest you type “make” and what files did “make” install?
The docs tell you to
perl Makefile.PL
make install
make initdb
Also the RTFM installation really had provlems - lots of ‘Unable to load
errors X from DBIx::Searchbuilder…’ errors… upgrading all the perl
modules fixed it and now it works fine…
Do you have a log of them? That would really help in tracking this down.
error: could not find component for path ‘/Elements/TitleBoxStart’
context:
…
15: %# GNU General Public License for more details.
16: %#
17: %# END LICENSE BLOCK
18:
19: <& /Elements/TitleBoxStart, title => loc(“[_1] newest articles”,
$rows), bodyclass=> ‘’ &>
20:
21:
22:
23:
…
code stack: /opt/rt3/share/html/RTFM/Elements/NewestArticles:19
/opt/rt3/share/html/RTFM/index.html:24
/opt/rt3/share/html/autohandler:247
-=| Ben
I’m pleased to announce the first release candidate of RTFM 2.2.0.
2.2.0 is a significant overhaul to RTFM that cuts out about 50% of the
application’s code and adds new features, increased stability and more
flexibility. (Basically, we took out all the bits where RT and RTFM did
similar things and made RTFM just use RT’s bits.)
You likely need RT 3.4.3 or newer to make use of RTFM 2.2.
‘make’ seems to install half the necessary, whereas ‘make install’ (as
documented) seems to install the rest. Might be worth noting in the
doco that ‘make’ will install a non working version.
Where did we suggest you type “make” and what files did “make” install?
The docs tell you to
perl Makefile.PL
make install
make initdb
FreeBSD ports… usual practice is
cd /usr/port/*/
make
make install
Having install RT that way and coming back to RTFM 2.0.4 I looked in the
README and it says just ‘make install’ however by force of habit I typed
‘make’ and noticed that it called install, so figured that it is just a
shortcut … big mistake… All I am saying, it might be worth
mentioning that ‘make’ will not install/do everything needed for a first
time install.
Also the RTFM installation really had provlems - lots of ‘Unable to load
errors X from DBIx::Searchbuilder…’ errors… upgrading all the perl
modules fixed it and now it works fine…
Do you have a log of them? That would really help in tracking this down.
No but all the errors we unable to AUTOLOAD errors.‘cannot find module’
etc…
On the subject of installing RTFM 2.2.0RC1 I have problems too.
I’m currently trying to get all extension into a demo RT environment
that is using SQLite and standalone_httpd so that I have everything in a
single directory.
I’m already using RTFM 2.1.37 in a test setup together with RT-3.4.3
which is working fine, it has been a continuing upgrade since 2.04.
I used SQL::Translator to get a schema.SQLite from schema.mysql. It is
installed properly into the demo SQLite database. When wanted to add a
couple of customfields for use with RTFM I noticed that I could’t select
‘RTFM articles’ from the pulldown menu in http://localhost:808/rt3/Admin/CustomFields/Modify.html?id=62
The others types are available (Tickets,Groups,Users,Ticket
Transactions,Assets).
OK back again to a clean install of RT-3.4.5pre1 and try again. Had a
look at the schema.* files from RTFM 2.2.0RC1 and saw only 4 tables in
there. In RTFM 2.0.4 there are quite a few more and if I look at
etc/upgrade/2.1.0 only 2 tables get added and in etc/upgrade/2.1.30 none
get added but there is a column change for Oracle only.
So if I have a blank install of RT and I add a new install of RTFM
2.2.0RC1 it can’t work. This is confirmed by the log of RT which
complains of missing customfields when admining RTFM.
Are there more people who tried from a cleanslate and found this or I’m
the only and therefore likely to make a mistake?
OK back again to a clean install of RT-3.4.5pre1 and try again. Had a
look at the schema.* files from RTFM 2.2.0RC1 and saw only 4 tables in
there. In RTFM 2.0.4 there are quite a few more and if I look at
etc/upgrade/2.1.0 only 2 tables get added and in etc/upgrade/2.1.30 none
get added but there is a column change for Oracle only.
So if I have a blank install of RT and I add a new install of RTFM
2.2.0RC1 it can’t work.
RTFM should only have a few tables now. We’ve removed most of them and
replaced em with equivalents from core RT.
OK back again to a clean install of RT-3.4.5pre1 and try again. Had a
look at the schema.* files from RTFM 2.2.0RC1 and saw only 4 tables in
there. In RTFM 2.0.4 there are quite a few more and if I look at
etc/upgrade/2.1.0 only 2 tables get added and in etc/upgrade/2.1.30 none
get added but there is a column change for Oracle only.
So if I have a blank install of RT and I add a new install of RTFM
2.2.0RC1 it can’t work.
RTFM should only have a few tables now. We’ve removed most of them and
replaced em with equivalents from core RT.
Good morning to you too
I have replaced the RT3.4.5pre1 with RT3.4.5rc2 and things are OK. Sorry
should have done that in the first place but haven’t had problems sofar
between RT versions and RTFM.
BTW, the drop_schema.* files are not correct yet, contains way to many
tables.
Which leads to another question: is it possible to drop the old RTFM,
now unused, tables?
I have replaced the RT3.4.5pre1 with RT3.4.5rc2 and things are OK. Sorry
should have done that in the first place but haven’t had problems sofar
between RT versions and RTFM.
Oh. That’s good to hear.
BTW, the drop_schema.* files are not correct yet, contains way to many
tables.
Which leads to another question: is it possible to drop the old RTFM,
now unused, tables?
I should probably sleep soon.