nsf43

Here you are...I know some may be direct quotes. However, just because the original author uses poor grammar, there is no need to propagate bad habits. 1) For the dates: "We will be closed..." use either ordinals or cardinals, no mixing We will be closed from the 18th of December, 2019 to the 7th of January, 2020 or We will be closed from December 18, 2019 to January 7, 2020 2) You can still use the website but orders cannot be placed until we reopen in the new year. 3) May not matter, but there is no Area Code in the phone number 4) Conflicting dates for "opening" 5) Place any message you want, here (remove "to" and add comma) 6) We are closed. (add period) In Product Info 1. It costs 5x as much to attract a new customer than it costs to keep an existing one. (Source: seohosting.com) Tweet this Stat! 2. 68% of lost customers leave brands because they are upset with the treatment they have received 3. On average, loyal customers are worth up to 10 times as much as the cost of their first purchase. 4. 48% of customers who had a negative experience told at least 10 or more others. 6. On Twitter, over 80% of customer service related tweets are negative or critical of the brand in question, a. A large 9. 68% of site viewers quit because of the attitude of indifference toward the customer 10. It's 6-7 times more expensive to acquire a new customer than it is to keep a current one. - This is redundant. Use either this one or #1. Try not to add confusion to the mix. (IBM will tell you this as well) 11. 3 in 5 Americans (59%) Either say 59%, or 3 in 5, not both because 3 in 5 is 60%. 12. 70% of buying experiences are based on how the customer feels they are either "the customers feel they", or "the customer feels he/she feels" 13. Customers who engage with companies over social media spend 20 -40% more money with those companies than other customers spend. 14. may causes unnecessary You need to Strike a happy medium and roll out updates only when absolutely required ( such as bug fixes ). New features should be planed in planned updates say every 6 or 12 months. If your you are rolling out updates every week, then many customers may just give up and not install them which and that defeats the whole purpose of doing the update.

Thx JcMagpie. I will happily edit anything you need.

Thx again...it is not protected. And yes, latest Phoenix. I am alternating between making sure the colors are right, adding products, and verifying text. I've done a couple of fake purchases, but still have Paypal in Sandbox mode. I am sure I will find things I missed as soon as I go Live ;). That was always the case with customers in the old days....

Thanks! I'm still not sure I will know which ones to choose since I am so new to this project. BTW, I'm in US. While I am aware of spelling differences between our versions of English (finalise and finalize), the grammar in some of the messages is incorrect. I majored in Math and English (the novel I'm reading has so many errors, it makes me crazy). If anyone cares, the grammar in my shop will be correct once I am officially live. (Should anyone want to copy). Also, is there anything special to do besides changing PayPal over to "live" in order to BE live?

In admin mode, upper right, there are messages "Install module(nn). Is one supposed to add all those modules, automatically? There is no indication of what is being installed. Having gotten almost to the point of going "live", I am a little nervous about adding these? Please advise. Thanks in advance!! Nancy

Well, that was painful! 3 more restarts and I finally saw the problem....when creating my own "admin", somehow a folder was marked unusable. It was not noticeable until I started comparing every file from my file server to the online version. And I suppose that is why one of the "configure.php" files did not get updated. Anyway, thanks for "listening" to my issues! Maybe it is smooth sailing from here.... Maybe you will find something to Buy!

I understand about not showing passwords, etc. But that is the least of my worries. Once I get this thing running as a whole, I shall fix things like that. I actually started over from scratch, building the DB. I have started from scratch multiple times now, as I am trying to have a clean build and install. This time, most of the visuals were good, so I started over on the DB build. There are a couple of odd things, but I can't fix them because of the 500. So, I have put in debug messages, trying to figure out where it stops. I posted that above. If I recopy just admin, the 500 goes away. But then weird things happen in the front end. It would seem that the admin code is trying to post an error into the "messsage_stack", but I do not know enough about the code to figure out what error has been raised. Then I noticed the configure.php was not getting filled in on the install. I hand added the database items, and perhaps the error is something like no path for Cookies, or some such.

Also, there are no paths in the configure.php files. Is that correct? I would have thought the "Install" feature would have filled these in. define('HTTP_SERVER', ''); // eg, http://localhost or - https://localhost should not be NULL for productive servers define('HTTPS_SERVER', ''); define('ENABLE_SSL', false); define('HTTP_COOKIE_DOMAIN', ''); define('HTTPS_COOKIE_DOMAIN', ''); define('HTTP_COOKIE_PATH', ''); define('HTTPS_COOKIE_PATH', ''); define('HTTP_CATALOG_SERVER', ''); define('HTTPS_CATALOG_SERVER', ''); define('ENABLE_SSL_CATALOG', 'true'); // secure webserver for catalog module define('DIR_FS_DOCUMENT_ROOT', $DOCUMENT_ROOT); // where your pages are located on the server. if $DOCUMENT_ROOT doesnt suit you, replace with your local path. (eg, /usr/local/apache/htdocs) define('DIR_WS_ADMIN', '/admin/'); define('DIR_WS_HTTPS_ADMIN', '/admin/'); define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN); define('DIR_WS_CATALOG', '/catalog/'); define('DIR_WS_HTTPS_CATALOG', '/catalog/'); define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . DIR_WS_CATALOG); define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/'); define('DIR_WS_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/'); define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/'); define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/'); define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/'); define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/'); define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/'); define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/'); // define our database connection define('DB_SERVER', 'localhost'); // eg, localhost - should not be empty for productive servers define('DB_SERVER_USERNAME', 'SparkyUser'); define('DB_SERVER_PASSWORD', 'Covington43'); define('DB_DATABASE', 'SparkyDB'); define('USE_PCONNECT', 'false'); define('STORE_SESSIONS', '');

It would appear that the app hangs trying to return from message_stack.php (admin/includes/classes/) in the function "add_session". Is this meaningful to anyone?

Thanks for the info. I had a 500 several years ago, and it turned out to be a typo in the DB - that must have lodged in my brain...meanwhile, I am still looking.

I'm back....sorry. Finally I have most of my cosmetic changes made. Then I started building my products. Stopped for the night. Next day, I try to return to admin and get the 500 Error. 3 times this has occurred. Each time, I rebuild and reinstall. The 500 goes away, until the next day when I want to add more products. I know a 500 is some sort of DB issue, when the host doesn't know what is wrong. However, I cannot spot the problem. I do not see anything wrong with the DB or code. I even built a new DB. Anyone have any thoughts? Thanks in advance!

Thanks,, Peter. What has made this exercise particularly frustrating is that I am a good CSS person! And I generally do clear cache in my programs with complex CSS. I sort of assumed clearing was already in the code - but we know about assume. So that is my bad. Then when I started over completely, I failed to put cache clearing in. Again, my bad. When I saw other people having the same issues, I over reacted and added everything people suggested. I am about to jump in and restore my DB and get my show on the road! Sorry I never got to Australia!

Good Grief! I quit checking other browsers because no one else mentioned anything browser specific (that I saw). So my "clear cache" code isn't doing the trick either. Thanks! So, should I put the "hooks.php" fix back in? or leave it out. Any other "css" gotchas?

added !important and cleared cache with clearstatcache(clear_realpath_cache); You see italic text?? and some color change?? what browser?

I have backed up previous code, backed up my DB and did a new upload of code. I ran the Install and did nothing else. Added to "user.css" for the text in the navbar to be italic, and the background color to be red. I also verified that "user.css" is the last stylesheet to be loaded. Nothing changed.