Hi
In general, I see that Ralf is answering queries on not just this mailing list. It must be very
time-consuming and at times repetitively boring to answer questions from users. Also many
users really do not put enough effort into providing information about their problem. I am
thankful (althouth I have not received answers to some of my questions) for any support I
got. On the other hand, it should be the community and not just the main developer
answering questions. It is also my observation that this list is going quieter. This could mean
that people have given up and just using the version that work for them or they turn to others.
We had a lot of trouble and no help from this list when we tried to upgrade from 1.8 to 14.1.
We gave up and then tried again to upgrade to 14.2 which worked (not smoothly though). We
are sitting in the same boat since we have been using EGW for a number of years and would
loose a lot of data to change to something else. Would I recommend it to others? NO!
The trouble is that when there are less CE installations, the community size drops and
subsequently the support (including development contributions). This will have an effect on
the paid version as well as those disgruntled CE users would not recommend it anymore -
word of mouth is powerful!!! Also, most would definitely not subscribe to the paid version as a
consequence of either business growth or having given up on the CE version. I would not.
Further, if there was an up-to-date user-guide/ Wiki, support would be a lot less. It would be
better to put more effort into the Wiki than producing video tutorials.
So far, despite having put many hours into this, we have not succeeded getting calendar
synchronisation to work (purchased an Android app). It would help if there were instructions
how the server must be set up.
Even more disheartening is the response from Stylite not to develop the “Sitemgr” module
any further. For a responsive front-end, they recommend to use yet another CMS. One of the
main reasons for choosing EGW was to have an all-in-one solution. Firstly, development
cycles between two major open source solution providers such as EGW and Typo3 for
example, are not coordintated. For a proper integration, the third-party CMS needs to be
providing the same access control as EGW which is often managed by an extension or
module. If one of the two has a major upgrade, this might stop working (talking from
experience!). Secondly, instead of just one major CMS, two need to be maintained.
Its very sad as EGW is really a great tool in general.
Gunda
------- Forwarded message follows -------
Date sent: Tue, 28 Jul 2015 18:18:56 +0000 (UTC)
egroupware-users@lists.sourceforge.net
please wait…
Send reply to: Kenneth Hawkins kjurkic@yahoo.ca,
discussions and questions from users and for users of eGroupWare
egroupware-users@lists.sourceforge.net
<egroupware-users.lists.sourceforge.net>
mailto:egroupware-users-request@lists.sourceforge.net?subject=unsubscribe
mailto:egroupware-users-request@lists.sourceforge.net?subject=subscribe
Hi
This list has been quiet for the last while - I cannot help as I have
not yet made the jump from 1.8 though we have to look at that some
time soon.
The only thin I can offer is to ask if you have confirmed the email
server settings - I had a problem with my initial setup where I had
not set the port number (SSL connection to SMTP)
cheersKen
EGW is a very useful collaboration tool, but the folks behind it
haven't really pushed for greater awareness in the IT world, so there
is not a as large a community for peer support as there is for a kit
like Zarafa, SOGo, or Citadel. Years ago, there was a couple of Linux
server distros that had EGW installed be default, but the lack of
marketing by Stylelite meant that the distro communities were being
asked for support, rather than directing their inquiries to this
list.
If I had to start over, I am not so sure I would go with EGW - there
are some default behaviors and engineering choices that were not fully
tested in a homogeneous network that have been causing a lot of grief
for me, and it appears that the jump to ver 14.2 is almost as much
work as jumping ship entirely for something that will play better with
OSX and Windows.
Sorry for the long digression, especially since it doesn't provide a
solution for you...
