Smarty Error when accessing Practice Settings

Management and Administration
21

drbowen wrote on Wednesday, April 05, 2006:

" To be honest I have never used Open source code before, I have always written my own and not really sure what I am allowed and not allowed to change or post. "

You are free to release your additions back into the source code.  We ask that you submit your code for review by one of the current active developers (Rod Roark, Andres Paglayan, Tekkno Genius, etc.).  The main purpose to check to make sure that your are being consistent with our current coding standards.

We also want all contributions to be made under the same type of licensing.  It would be nice if you start your code section with your name and  contact information, followed by a specific statement that you are releasing your contribution under the terms of the Gnu General Public License.
(GPL for short).

If you make some contributions, and the current developers are convinced that you are not unintentionally introducing bugs, then they can and will extend direct commit privileges to you.

The reason I made the statement about “Don’t do all this work on something you don’t intend to use in production.” is that I know human nature.  They great majority of OpenEMR users are small offices that do not have professional IT support.  Getting everything installed and working correctly is somewhat time consuming.  Most physicians are not going to have the patience for this.

If you ARE a professional IT support admin, then the more cautious install on Windows XP Pro, makes sense.  The reality is that installation of OpenEMR in the webroot doesn’t affect the function configuration of the server at all.  It can be added or removed with impunity.

Installing Apache, MySQL, PHP and PERL do affect the server configuration but already have long track records of security.  Installing these do affect security to some degree but patching your server for security on a regular basis helps minimize this type of risk.

So my recommendation about going about this on your live server has been reasoned out.  I think it can be done with minimal security risk to the server.  Plus there is nothing quite so frustrating as getting everything working great on a slow test machine and then turning around and not being able to get things working on the main server. (been there, done that)

Sam Bwoen, MD

22

drbowen wrote on Wednesday, April 05, 2006:

The other issue that has not been addressed yet is that unpacking a .tar.gz file does not always work using WinZip.  It tends to want to open using line breaks.  This doesn’t cause any trouble when opening a Windows file but can cause trouble when opening a Unix/Linux compressed file.

I am currently uncompressing openemr.2.8.1.tar.gz in Linux and will repackage it as a .zip using the Windows tools.  This will be posted shortly at www.oemr.org.

Sam Bowen, MD

23

hukutas wrote on Thursday, April 06, 2006:

I do most of my coding on a large AIX machine and I do unpackage everything on the AIX machine as I was somewhat hesitant to unzip with winzip.

I us a product called installshield to repackage an msiexec for the windows runtime. This way when it is complete I can bundle it and setup an autoupdate server and set (during install time)a auto update Key to the product to an update server, thus allowing the windows 2003 machine to schedule to check for updates in the evenings.

Then I simply will push my changes up to my update server and it should work fine.

At least this is the plan…We will see

24

hukutas wrote on Thursday, April 06, 2006:

Ok

Win XP Pro SP 2
xampp-win32-1.4.13
OpenEmr 2.8.1
Mysql 4.1
PHP 4

No More Smarty Errors

Had to alter globals.php to

$webserver_root = "C:\\xampp\\htdocs\\openemr";

This corrected my Smarty Errors.

Thanks Everyone for the help

25

drbowen wrote on Thursday, April 06, 2006:

I updated the packages on oemr.org to 2.8.1.

402ce7b8d2b2836ce769da9e4effbe59 : openemr-2.8.1.tar.gz
ce4ad05d0434b5bc16ffe3438d910dcd : openemr-2.8.1.zip     

I will post a bzip2 file a bit later.

Thanks for the tip on the back slashes, Rod.

I’m going to update the HOWTO to include the double back slashes.

Sam Bowen, MD

26

hukutas wrote on Thursday, April 06, 2006:

Rod,

  Thanks for not ony the backslash tip but link to http://www.php.net/manual/en/language.types.string.php

Also I want to thank everyone who posted.

Thanks Again

27

drbowen wrote on Thursday, April 06, 2006:

I am glad we had this discussion.

Part of the instructions were missing from the wiki

http://www.oemr.org/modules/wiwimod/

because of the the way the CMS was handling the <?PHP  characters.

I have removed the offending characters and the missing instructions are now visible.  I also added double backslashes per Rod’s tip.

Sam Bowen, MD

28

hukutas wrote on Thursday, April 06, 2006:

Well If you are glad we dicussed this, Just wait next I am off to duplicate this setup on the Sever 2003 machine and get it working, Also I intend to try and get postgre, Freeb, sqlLedger, and fax working on the server.

So I am sure I will run into all sorts of issues !!

The fun starts this weekend…

Note - I havent seen any doco’s on setting up postgre, Freeb, sqlLedger, and fax on Windows 2003 server (Maybe I am just missing it) if there is any a point in the right direction would certainly help.

If not I of course am going to document every step I take and when I get it working I will post how I was able to pull it off.

Again Thanks.

29

drbowen wrote on Thursday, April 06, 2006:

I haven’t had the time to personally tackle this set-up.

I would appreciate you’re keeping careful notes as you go along.  If you would them to me I can include this in the documentation.

(I have been the main person writing documentation.)

Of course if you are a registered user at oemr.org you can make the posts there as well.  The editor is HTML sensitive so to get things to appear correctly you have to some times use the HTML character symbols.

Sam Bowen, MD

30

hukutas wrote on Thursday, April 06, 2006:

I will send you my doco when I complete the server 2003 install setup. This way you can look it over before it gets posted.

It turns out I am not really good with writing the doco. I will make a flow chart of all the steps I take and forward the document to you so you can go over it and then post it when you feel it is complete and accurate.

31

drbowen wrote on Thursday, April 06, 2006:

If you can record the commands as you go, I can do the rest.

Thanks.

32

hukutas wrote on Thursday, April 06, 2006:

Will Do