Through some local testing, I've found that it is not practical to do our
upgrade checks within our built in script because it is run too late in the
sequence. To get around that, I've built a stand alone application that can
be used to do the checks and alert users to the status of their host's
support for J! 3.0. That app can be found at
https://github.com/mbabker/J30UpgradeCheck and has the instructions for use
included. Feel free to use it and report bugs to me via the repo's tracker.
So it is clear for all, this is as lightweight of a package as possible. To
get it there, only the necessary library classes are included and all
translations have been removed, so the tool is hard-coded to English.
Otherwise, it is the same information reported in the installation
application if your site is not compatible.
I finally had a chance to test this on my servers and it works flawlessly.
Thanks for putting this together and keep up the great work! Hopefully this
can be used as part of a migration tool at some point.
On Mon, Sep 10, 2012 at 5:12 PM, Michael Babker <mbab...@flbab.com> wrote:
> Hello,
> Through some local testing, I've found that it is not practical to do our
> upgrade checks within our built in script because it is run too late in the
> sequence. To get around that, I've built a stand alone application that
> can be used to do the checks and alert users to the status of their host's
> support for J! 3.0. That app can be found at
> https://github.com/mbabker/J30UpgradeCheck and has the instructions for
> use included. Feel free to use it and report bugs to me via the repo's
> tracker.
> So it is clear for all, this is as lightweight of a package as possible.
> To get it there, only the necessary library classes are included and all
> translations have been removed, so the tool is hard-coded to English.
> Otherwise, it is the same information reported in the installation
> application if your site is not compatible.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! bug Squad" group.
> To post to this group, send email to joomlabugsquad@googlegroups.com.
> To unsubscribe from this group, send email to
> joomlabugsquad+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomlabugsquad?hl=en.
Downloaded Used the Hosts file manager to upload and unzip Files were set at 666 Reset files 644 Pointed browser at the directory Full success
Unzipped locally and ftp'd up files were correct Pointed browser at the directory Full success
configuration.php showed 'No'(of course) Display errors showed 'Actual On' ... not sure about that ... which display errors, php.ini or Joomla's ? Output Buffering 'Off' ... again not sure about that setting as the installer in kickstart says recommended 'Off' doesn't it ?
On Monday, 10 September 2012 22:12:09 UTC+1, Michael Babker wrote:
> Hello,
> Through some local testing, I've found that it is not practical to do our > upgrade checks within our built in script because it is run too late in the > sequence. To get around that, I've built a stand alone application that > can be used to do the checks and alert users to the status of their host's > support for J! 3.0. That app can be found at > https://github.com/mbabker/J30UpgradeCheck and has the instructions for > use included. Feel free to use it and report bugs to me via the repo's > tracker.
> So it is clear for all, this is as lightweight of a package as possible. > To get it there, only the necessary library classes are included and all > translations have been removed, so the tool is hard-coded to English. > Otherwise, it is the same information reported in the installation > application if your site is not compatible.
That's odd about the file permissions. I just checked my local system and
the file permissions are set properly here. I do remember someone
mentioning that ZIP files from GitHub came down with 666 permissions (or
something that wasn't 644), so that may be the problem.
As to the rest of it, I can double check to make sure the checks are in
sync, but it should be using the same model method from the CMS install app.
From: Kevin <i...@weblinksonline.co.uk>
Reply-To: <joomlabugsquad@googlegroups.com>
Date: Friday, October 5, 2012 6:34 PM
To: <joomlabugsquad@googlegroups.com>
Subject: [jbs] Re: Upgrade Check Application
Downloaded
Used the Hosts file manager to upload and unzip
Files were set at 666
Reset files 644
Pointed browser at the directory
Full success
Unzipped locally and ftp'd up
files were correct Pointed browser at the directory
Full success
configuration.php showed 'No'(of course)
Display errors showed 'Actual On' ... not sure about that ... which display
errors, php.ini or Joomla's ?
Output Buffering 'Off' ... again not sure about that setting as the
installer in kickstart says recommended 'Off' doesn't it ?
On Monday, 10 September 2012 22:12:09 UTC+1, Michael Babker wrote:
> Hello,
> Through some local testing, I've found that it is not practical to do our
> upgrade checks within our built in script because it is run too late in the
> sequence. To get around that, I've built a stand alone application that can
> be used to do the checks and alert users to the status of their host's support
> for J! 3.0. That app can be found at
> https://github.com/mbabker/J30UpgradeCheck and has the instructions for use
> included. Feel free to use it and report bugs to me via the repo's tracker.
> So it is clear for all, this is as lightweight of a package as possible. To
> get it there, only the necessary library classes are included and all
> translations have been removed, so the tool is hard-coded to English.
> Otherwise, it is the same information reported in the installation application
> if your site is not compatible.
-- You received this message because you are subscribed to the Google Groups
"Joomla! bug Squad" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/joomlabugsquad/-/iZvReB2mkwwJ.
To post to this group, send email to joomlabugsquad@googlegroups.com.
To unsubscribe from this group, send email to
joomlabugsquad+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/joomlabugsquad?hl=en.
The file permissions are probably due to my shared Hosting. The file manager in my Host's CP creates ta new folder 711 ... then when I unzip the zip file a cgi file is placed in the folder ... pointing the browser at the cgi file returns a message the file permissions are not correct. Then after changing the chmod to of the folder to 755 the cgi runs when pointed to in the browser. And the zip file gets unzipped. ... the unzipped folders are 755 and files 666.
It must be a problem on the Host side because uploading the unzipped files results in the correct permissions fot folders and files. it is very inexpensive Hosting but serves me well (most of the time) and Joomla runs well on it.
"* but it should be using the same model method from the CMS install app*." Joomla install gives the same results for buffering ... it's the install packed in the jpa file that recommends Off. If memory serves me correct J1.5 used to recommend Off ? But 2.5 recommends On like your app.
Anyway ... it worked on a cheap/inexpensive shared Hosting :D
On Saturday, 6 October 2012 03:02:16 UTC+1, Michael Babker wrote:
> That's odd about the file permissions. I just checked my local system and > the file permissions are set properly here. I do remember someone > mentioning that ZIP files from GitHub came down with 666 permissions (or > something that wasn't 644), so that may be the problem.
> As to the rest of it, I can double check to make sure the checks are in > sync, but it should be using the same model method from the CMS install app.
> From: Kevin <in...@weblinksonline.co.uk <javascript:>> > Reply-To: <joomlab...@googlegroups.com <javascript:>> > Date: Friday, October 5, 2012 6:34 PM > To: <joomlab...@googlegroups.com <javascript:>> > Subject: [jbs] Re: Upgrade Check Application
> Downloaded > Used the Hosts file manager to upload and unzip > Files were set at 666 > Reset files 644 > Pointed browser at the directory > Full success
> Unzipped locally and ftp'd up > files were correct > Pointed browser at the directory > Full success
> configuration.php showed 'No'(of course) > Display errors showed 'Actual On' ... not sure about that ... which > display errors, php.ini or Joomla's ? > Output Buffering 'Off' ... again not sure about that setting as the > installer in kickstart says recommended 'Off' doesn't it ?
> However it looks great and reports well.
> On Monday, 10 September 2012 22:12:09 UTC+1, Michael Babker wrote:
>> Hello,
>> Through some local testing, I've found that it is not practical to do our >> upgrade checks within our built in script because it is run too late in the >> sequence. To get around that, I've built a stand alone application that >> can be used to do the checks and alert users to the status of their host's >> support for J! 3.0. That app can be found at >> https://github.com/mbabker/J30UpgradeCheck and has the instructions for >> use included. Feel free to use it and report bugs to me via the repo's >> tracker.
>> So it is clear for all, this is as lightweight of a package as possible. >> To get it there, only the necessary library classes are included and all >> translations have been removed, so the tool is hard-coded to English. >> Otherwise, it is the same information reported in the installation >> application if your site is not compatible.
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/joomlabugsquad/-/iZvReB2mkwwJ. > To post to this group, send email to joomlab...@googlegroups.com<javascript:> > . > To unsubscribe from this group, send email to > joomlabugsqua...@googlegroups.com <javascript:>. > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
