The open atrium website states that it has been tested using php 5.2
but I am unable to install the code getting the following error
[18-Jun-2013 20:18:42] PHP Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/xxxxx/public_html/qqq/profiles/openatrium/modules/contrib/date_ical/includes/DateIcalFeedsParser.inc on line 32
Is the :: syntax not a PHP 5.3 thing
Would it be possible to install an odler version DateIcalFeedsParser to try and get the system to install on php 5.2
this has also been reported in https://drupal.org/node/2008756 but in that case the poster was able to update php to 5.3
I am on shared hosting and cannot update the version of PHP
If 5.3 is a minimum requirement please update your system requirements page accordingly
Comments
Comment #1
mpotter commentedSince that is an error in the date_ical module, it should be reported there and not here so it can get fixed. However, I can certainly increase the requirements for the oa_events plugin to require PHP 5.3.
Fortunately I think this is only an issue for the Feeds importer, so I might separate the oa_events_import into a separate project so people who don't need the iCal import functionality can still use oa_events without PHP 5.3.
If this gets fixed in date_ical module, please post the issue link here so I can update OA2 to use the correct version.
Comment #2
mpotter commentedComment #3
FranCarstens commentedIt appears the date_ical module is for php5.3 and they're not supporting php5.2.
How do I go about installing Atrium without this functionality?
Comment #4
mpotter commentedoa_events_import is now a separate module, so remove that module from your OA2 installation and then it should be fine.
Don't plan any additional action on this in OA2 however. As I said, it's really something that needs addressing in the Date iCal module.
Comment #5
jimdoria commentedCan you provide more info on how to remove the module? There's no option in the setup process to disable individual modules, and simply deleting the files for the module causes setup to fail, at least once the installation has started.
Should I delete everything and re-run setup on a clean install from which I've already removed the module? Can I run setup to completion without PHP 5.3 that way?
Comment #6
jimdoria commentedOK, well I tried re-installing from scratch with the module removed and that didn't work either. The Verify Requirements step of setup shows that the module is missing and won't proceed without it. So I'm still not sure how to remove this module from OA and get on with setting it up.
Comment #7
jimdoria commentedFWIW, I was able to work around this and get past the Install Profile step with PHP 5.2.17.
I did the following:
/profiles/openatrium/I edited theopenatrium.infofile and put a semicolon in front ofdependencies[] = oa_events_import(line 123)/profiles/openatrium/modules/contrib/oa_events/I edited theoa_events.infofile and put a semicolon in front ofdependencies[] = date_ical(line 10)date_icalfrom the/profiles/openatrium/modules/contrib/folder, but this may have been unnecessary. It may be that just commenting out the dependencies from the.infofiles is enough, since I didn't have to delete theoa_eventsfolder.Comment #8
khayam shah commentedhello there i am facing this error while installing open atrium ......
what can i do to fix this error
plz reply me as soon as possible
thnx
Comment #9
khayam shah commentedi am facing this error
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'openatrium.search_api_server' doesn't exist
please guide me about this
Comment #10
tkosars commented@jimdoria:
Thanks for the tip, the installer just finished installing the profile. Btw step 3 is not necessary since you've removed all references for the date_ical module in steps 1 and 2.
Comment #11
greta_drupal commentedWhew! Much obliged for this hack, jimdoria. Step 3 does appear to be necessary. I tried with only remarking the depencies in info files, and installation still failed. After deleting the folder, it installed. Too bad the distro includes these breaking modules.
Comment #12
FranCarstens commentedExcellent!
Comment #13
Argus commentedTagging for documentation purposes.