Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Aalst

Archived
  • Posts

    197
  • Joined

  • Last visited

Everything posted by Aalst

  1. I believe it still displays the full price in the tool as a reference, it was a much more simple approach. However, when the e-mail is sent no pricing is sent since it is a customer service (soft sell) message. As for the triplicate issue I do not really understand. Can you provide a link to a screen shot of the issue?
  2. There is a date stamp for the cart, I always wait at least 1 day before sending them a message. This prevents me from contacting soming in the process of shopping, and if someone maybe coming back that same day. The chances of someone saving the cart for a future purchase is very very low. However as the message is worded they would not be offended by it and would most likely just let you know they are planning on returning. That is because it doesn't take up hardly any space in the DB and there is no REAL need to delete or "flush" the information that RCS adds. The carts being saved in the DB is a function of the CORE OSC and is not something that RCS added. The scart Table only containts two int(11)'s and a varchar(8) and I have been running this for over 6 months and I only have 4k of data in that table. I think if you look back a few pages of this topic you will see where JM posted how much space his scart table holds and he created this tool and the previous report and has more data in there than anyone and it actual space was used was nothing. If you want to flush it, which I don't recommend, you can use what ever tool your host provides most likely phpMyAdmin and then just "Empty" the scart table. -Aalst
  3. JM... that is the link I was looking for... I couldn't find it, so I just reposted the info here... >shurg<
  4. Again I don't recommend running a RCS version with delete features. This is off topic but here is how you do it: First you need to add a new line to the language file stats_customers.php in at least the language(s) you use. (admin/includes/languages/english/) Find the line: define('TABLE_HEADING_CUSTOMERS', 'Customers'); Then add this line below it: define('TABLE_HEADING_ORDERS', 'Orders'); Next you need to edit the file /admin/stats_customers.php and find the line (around line 55): <td class="dataTableHeadingContent"><?php echo TABLE_HEADING_CUSTOMERS; ?></td> Then add this line below it: <td class="dataTableHeadingContent" align=center><?php echo TABLE_HEADING_ORDERS; ?></td> Then find this next line (around line 60): $customers_query_raw = "select c.customers_firstname, c.customers_lastname, sum(op.products_quantity * op.final_price) as ordersum from " . TABLE_CUSTOMERS . " c, " . TABLE_ORDERS_PRODUCTS . " op, " . TABLE_ORDERS . " o where c.customers_id = o.customers_id and o.orders_id = op.orders_id group by c.customers_firstname, c.customers_lastname order by ordersum DESC"; Replace that line with this one: $customers_query_raw = "select c.customers_firstname, c.customers_lastname, sum(op.products_quantity * op.final_price) as ordersum, c.customers_id as cid from " . TABLE_CUSTOMERS . " c, " . TABLE_ORDERS_PRODUCTS . " op, " . TABLE_ORDERS . " o where c.customers_id = o.customers_id and o.orders_id = op.orders_id group by c.customers_firstname, c.customers_lastname order by ordersum DESC"; Next find the following line (around line 69): while ($customers = tep_db_fetch_array($customers_query)) { Right after this line add the following lines: $customers_query_numords = tep_db_query("select orders_id from " . TABLE_ORDERS . " where customers_id ='".$customers['cid']."' "); $orders = tep_db_num_rows($customers_query_numords); Finally find this line (around line 80): <td class="dataTableContent"><?php echo '<a href="' . tep_href_link(FILENAME_CUSTOMERS, 'search=' . $customers['customers_lastname'], 'NONSSL') . '">' . $customers['customers_firstname'] . ' ' . $customers['customers_lastname'] . '</a>'; ?></td> And add the following line after it: <td class="dataTableContent" align=center><?php echo $orders; ?></td> Presto... you know have a new column on your Customer Orders-Total report showing who your best customers are by dollar amount, and also showing the number of orders they have made to get that dollar amount. I hope that helps you...
  5. It has No Hyperlinks and No Prices since I been involved in with RCS. It is just a simple plain text message. Feel free to add those features if you wish.
  6. It is sent as PLAIN TEXT and has only new lines for formating. If when you get the message it should have empty lines seperating information so that it is easier to read. This is normal and the safest way to send the message so that everyone can read it. If it is coming in some other way, check to see what method your server is using to send messages and see if can possibly be changing the message, or check your e-mail software you use to view it to see if it is removing lines or something.
  7. This gives more info that the one I previous replied to. However RCS just gives it's customer request to: /admin/customers.php The search is then being handled by that file. The RCS tool just provides a LAST name for the search. You would have to trouble shoot the customers.php file as to why it doing this. I have tried and cannot replicate this issue.
  8. JM -- apparently Willross released a 1.4 version of RCS on March 31st 2004 and he says in the comments that he "Added 'delete' feature in two places" He doesn't say where those two places are and I am not using 1.4. Saletco -- You may want to see if you can contact Willross some how, see if he put contact info in the readme of 1.4. Anything realted to changes in 1.4 I do not know anything about and it sounds like JM has it used it either.
  9. where NAME = the name searched for. That error shouldn't be related to RCS, because you can't search for a customer in it. Sounds like you are getting this error in another part of OSC like the Customer Admin. If so this can't be related to RCS unless during the install you mistakely changed something dealing with the customer admin.
  10. JM -- Tsk tsk.. it still a good idea as long as it is optional. Here is a hack to add what ever greating you want in front of the name. First you need to add a new line to the language file recover_cart_sales.php in at least the language(s) you use. (admin/includes/languages/english/) Find the line: define('EMAIL_TEXT_SUBJECT', 'Inquiry from '. STORE_NAME ); Then add this line below it: define('EMAIL_TEXT_EMAIL_TEXT_SALUTATION', 'Dear ' ); You can change the greeting from "Dear" to what ever you want just make sure there is a space after it, or just leave it empty for no greeting if you change your mind in the future. I think if this is included in a future release it should be empty by default. Next you need to edit the file /admin/recover_cart_sales.php and search for the text: $email = $inrec['fname'] . ","; [code] It should be around 234 in version 1.3.6a. Replace that text with this: [code] $email = EMAIL_TEXT_SALUTATION . $inrec['fname'] . ","; Presto... you know have a Salutation of your choice before the users first name. Now I agree with JM about not using this, however, the above hack will allow you to do it if you want, and easily remove it if you change your mind in the future. AS for the DB Flushing that was a comment listed on the 1.4 release and I agree with JM that I do not see who the RCS data would need this unless some how you are using MySQL and hitting the 4gb limit on the Table size which would be hard to do. You would have to ask Willross who released 1.4 why he makes the claim that "YOU MUST FLUSH OUT THE 'scart' DB OCCASIONALLY!" because again I agree with JM on the scart specific data is minor and would be very difficult to hit the table size limitations with it. Because Willross says it will prevent uncontacted errors, well I have not had any uncontacted errors. Anyway... good luck with the hack if you use it. -Rodney [Hopefully who ever does the next release will include this in it, if I do not get around to it :)]
  11. Now that is a good suggestion. I will post the "hack" below, since I have not looked at RSC 1.4 yet, I am still running 1.3.6a, and I do not have the time to make a full fledge release. You will need to edit two php text files. First you need to add a new line to the language file recover_cart_sales.php in at least the language(s) you use. (admin/includes/languages/english/) Find the line: define('PSMSG', 'Additional PS Message: '); Then add this line below it: define('PSMSG_DEFAULT_TEXT', 'Default Text'); Change the "Default Text" to what ever you want, or even leave it blank. Next you need to edit the file /admin/recover_cart_sales.php and search for the text: tep_draw_textarea_field('message', 'soft', '80', '5') It should be around 447 in version 1.3.6a. Replace that text with this: tep_draw_textarea_field('message', 'soft', '80', '5', PSMSG_DEFAULT_TEXT) Presto... you know have a PS Message default text. Good Luck... -Aalst [Hopefully who ever does the next release will include this in it, if I do not get around to it :)]
  12. Keep in mind that this is my personal opinion, BUT.... First they are not "hard coded", so if a "newbie" can't edit a text file they shouldn't be using OS Commerce. Most of the customizing of the core OSC requires the editing of text files that we like to call language files. By the way, how did you get RCS installed if you find editing a text file "too difficult" for you? I would think the install is more difficult that editing a text file with notepad, but that's me. With that said, the file recover_cart_sales.php doesn't take a high level tech degree to comprehend. It is in plan English. If you want to change the subject, then change the text for "EMAIL_TEXT_SUBJECT". If you want to change the message body change the "EMAIL_TEXT_CURCUST_INTRO" and/or EMAIL_TEXT_COMMON_BODY. They are in a language file that is no more complicated than the old Windows INI files. They are separated from the main code, so that they would not be hard coded. That is one of the many things the language files are for. To create an admin for these simple tasks would be a big task. It would require that these items be moved to the database, and it would have to be able to support all languages. Then they would require DB calls to get this information. One of the goals is to keep unneeded DB calls down. This admin you are asking for not only would complicate a the install of the product, it complicates the coding, and it risks slowing the display of information down. Oh by the way... DB is short for DataBase. Now I know I have not posted for a while, but I couldn't let any of you forget my sarcastic posts. I am sorry the one who said there is no stupid questions hasn't been to America in the last twenty years. :) Adios...
  13. There is nothing wrong with deleting customers. You have to clean house and do customer maintenance from time to time, as a matter of fact Met00 is working on a customer tool, that will be RCS aware, it may be easier for it to handle this feature when a customer is deleted using this new tool. What do you think Met00?
  14. Try reading this topic before posting, you may find answers to questions before having to post. You will find the answer to your question posted at least once. OOoh was that snippy?
  15. Okay this is posted in the forums already, this is an error in the 1.3.6 README. you need to change: define('FILENAME_STATS_RECOVER_CART_SALES', 'stats_recover_cart_sales.php'); to: define('FILENAME_REPORT_RECOVER_CART_SALES', 'stats_recover_cart_sales.php'); This is step 4a for MS2. I guess I will up date a 1.3.6a version to update the readme. It should be posted in moments... :)
  16. That is off topic, and I know Met00 stated as such in his post. :P You can check out http://wiki.oscommerce.com for support documentation about how to make changes to your language files, as well as other interesting things you may want to learn about OSC. We should try to keep post that are not related in some way to the RCS tool out of this topic. If they are not RCS related in some way they should be directed to an appropriate topic, PM the person you wish to ask the question to, or start a new topic. Just in a little over 2 weeks we have already generated a very long topic (136 posts including this one). It makes it difficult for new comers to keep up if they have to go through all this. Now I am not saying we should drop the humor, Heven (or that other place) forbid, if it is at least remotely related to the RCS tool. :) Just questions about: ?How to do this? or ?how to do that?, which have nothing to do with the tool. Most likely if someone just did a search in the forums they would find the answer, or if they checked out the Wiki Documentation. This now concludes part one of the Obnoxious Articulation as performed by Aalst the Rude and Short Tempered, to hear more please insert the Eight Track tape labeled part two.
  17. That is what it says it is an internal server error. You need to contact your hosting provider for tech support. This is not caused by a PHP script directly, this is an error from your SERVER. That is why it can tell you the e-mail address of the one to contact about the problem. PHP would have no idea how to provide this information to you. I would recommend you follow the instructions on the error message, and also follow your hosts normal support procedures.
  18. You snip'd my disortation! Hooooooooooooow Daaare You! :D Also SNIP is not the best word to use in or arround guys. :o :unsure: BTW you are showing a profound side we have not see before. STOP IT! :)
  19. Sounds like a great way to get more detail information from clients. However, I think this is not the most efficent way to expend effort. Let me tell you why. My personal bielf in coding, is DO NOT RE-INVENT THE WHEEL. This simple statement means that before I code anything I do a search for Open Source, Freeware, Shareware, and Commercial software that does what I am thinking of. If it is Open Source or free in some way and it does the job, then there is no need to expend the effort to start from scratch and write my own code that takes lots of time, and QA, etc etc. If it is a Commercial package and there is no other type availane and the price is reasonable, I will buy. If it is over priced and it is within my ability to code, then I will write. So far I rarely had to resort to writing my own applications for myself. I have found good software that does what I need. Usually several choices to pick from. In the case of a survey HTML e-mail, well there are several free and paid services that will host a survey for you, and keep all the data for you and also provide all the charts you chould ever want. If you register for one of these services then you can provide a link to the survey page and change the text e-mail to ask the user to take the survey. If you create a survey and someone integrates it into the RCS Tool then it would require new DB Tables, and its several Reports just for this. It would also need its own Admin tool just to handle the questions to make it easy for users to add and remove them and to handle the answers and linking questions to other questions and etc etc. It snowballs from a simple good idea into several and then it creates a life of its own. My view is that there are several good servey tools/services out there that can be easily used with this Tool so why RE-INVENT them in trying to implement your own version into it. Remember all statements made in this post are the sole opinion of Aalst. OSC, This Topic, and Met00 are not responsible for them.
  20. Keep in mind the my interpretation of the intentions of the tool is for a CUSTOMER SERVICE approach. That doesn't mean that you can't not use it to soft sell or even hard sell the people. Keep in mind you may most likely be cross the line from a welcomed e-mail to a another piece of SPAM. Also you may be break some laws depending on the country and region your business is based in. This is the safest way to package a tool for general use by a mass majority of OSC users. You are encouraged to change the message to what every you want or need. You just need to change the appropriate language file. Maybe a new TOPIC could be started for people to post just these types of message so we could have a collection of them for users to pull from.
  21. Personally I do not think the tool was designed to be used to process such a long period of time. Think about it... You only want to contact people who have abandoned their carts with in a recent time frame. Like 10 days, which is the default, I personally use a 5 day rule. I do not contact abandoned carts over 5 days old. However I never let them get that old. I check everyday, and then process carts only after they are over 24 hours old. You want to contact the client while the experience is fresh in their minds. You don't want them to forget about what they wanted and why. You never want to contact stale leads. Also clients will think it is an honest customer service inquiry if it is within 48 hours. Older than that and they may get suspicious of your true motives. When you run the tool for the first time, you may want to JUST LOOK at a large time period like 60 or 90 days, just to see the amount of abandoned carts that have gone to waste. However to contact a client about something that happened 2 weeks ago let alone 2 months ago is ridiculous. Therefore after you give over the pure awe of the amount of wasted opportunities, set it to 5 days and go from there and then try to check on a reoccurring regular basis. Also never respond RIGHT away to an abandoned cart. They are not really abandoned until at least an hour or two have passed. Why? Well as soon as someone places an item in there cart (and is logged in) it will show up on this report. That means a person could still be shopping, and making choices. To contact them while they are doing this may cost you the sale. Also some times a shopper likes to save their cart with what they want and then buy it later that day or the next. (My wife does this all the time on sites that save carts). Then and thereby if you wait at least an hour or two you have a good chance that it is an abandoned cart. I like 24 hours to make it look more like a customer service inquiry, than a desperate attempt at reclaiming a lost sale. Therefore you can clearly see that having pages implemented in to the tool would be a low priority on the list of new features, because if checked everyday it should be a manageable list. Keep in mind this is how *I* use the tool and the methods I have implemented to govern that use. Met00 may have other ideas in mind when he created it of how the tool should be used, which I would like to hear, since he has tons of good ideas. Regardless, I hope this helps you and others who may be wondering how to use the tool. As for the report since it doesn't work yet, I have no idea how to use it. :D
  22. Met00, Hey are we a little touchy? hehe :) (Bowing down to Met00) OKAY EVERYBODY... LISTEN UP... MET00 IS THE GENIUS BEHIND THE REPORT, THE TOOL, THE IDEAS! I am the uncreative one, the grunt programmer, the one ruled by standards, and conformity. I just like to help. :D As I like to say: Now stop giving me credit for Met00 work, and ideas. :D :P
  23. Yes that is a known defect in Woman 1.0, it usualy had lower occurences in the Asian model. Yep, that's is the standard error message for this defect . We've been having trouble getting the upgrades implement. Man 1.0 is very stuborn. As long as this Woman 1.0 was Licensed to you this defect should not have occured we implementing that. It typically occurs when some does this to an unlicensed version of Woman 1.0. This is a good treatment, however it only relieves the symptoms for a short period of time. This to is an unfortunate side effect that occures after you purchase your license for Woman 1.0. Thats would be a POWER D cord followed by a A to E progression. Good Luck ... :o :huh: ;) :lol: :D :P B) :rolleyes: <_< :( :angry: :) :unsure: :( :ph34r: :blink:
  24. Well the error was in a mistake in the README, nothing was wrong with the files themselves. If 1.3.5 was working then no need to go to 1.3.6. Also you never provided details on what was not working and the exact error message you where given after trying to use 1.3.6. You also never SAID what wasn't working the REPORT or the TOOL. Because you just said "it" wasn't working CORRECT, and "the" file name was wrong in APPLICATION_TOP.PHP which isn't possible if correctly installed with version. Also you can't be using 1.2 or higher because it will not work when you go to the report (NOT THE TOOL) with the defines in the readme's from those versions. You must somehow still be using 1.0 or 1.01 that used thsoe defines. Or you are have not tryed to access the REPORT which is where an error would come up. The PHP files are fine, then only change was documented in a post just prior to the release of 1.3.6 post. Everything in the TOOL would work fine with 1.2 through 1.3.5 until you try to use the report, if installed per the readme. It would not be able to find the report, UNLESS the define was in filenanames.php (for MS2) or application_top.php (for MS1) was corrected. Installing 1.3.6 should not have done anything, since no code was changed in the files, ONLY the readme file was changed. I would recommend DELETING ALL your RCS Tool files from any and all version: /catalog/admin/recover_cart_sales.php /catalog/admin/stats_recover_cart_sales.php /catalog/admin/report_recover_cart_sales.php /catalog/admin/includes/languages\<language>\recover_cart_sales.php /catalog/admin/includes/languages\<language>\stats_recover_cart_sales.php /catalog/admin/includes/languages\<language>\report_recover_cart_sales.php Then make sure you remove any changes to CORE OSC files from all previous installs of the tool by using the readme's from each version. Make sure you have a clean removal. Then using 1.3.6, reinstall per the instructions and it should all be fine. FYI, for anyone: In the future to save time when posting a request for help or support for anything anywhere below is a list of general guidelines that usually help expidite the process. Most should be applicable to just about any problem you may have and need help with. General Guidelines What the problem is Error message(s) if any Your version of OSC (Or Main Application) Your version of the item you need help with if any Have you tried to troubleshoot, and if so what where the results Anything you may have done in an attempt to correct the problem Is it intermittent or does it happen everytime How much wood could a woodchuck chuck if a woodchuck could chuck wood? -Aalst
  25. Thank you, however I am sorry to say that I am A LOT confused by your message. I think I can assume you are using the tool since you consider it great. However you say you are afraid to use it. Why are you afraid to use it, especially if you have been using it? Then you really lose me when you talk about changing from 1.3.5 to 1.3.6 and you say you recognized it wasn't working before it was working. So you changed "IT" back to ... then you provide me with the file names and database table defines. Was 1.3.5 ever working for you? Was 1.3.6 ever working for you? Is one of the versions working for you right now and if so which one? What is this IT you changed back? What was IT before and What is IT now? Does IT have something to do with your filenames or database? From your copy and pastes of the defines can I assume you are on MS1? What is the problem you are having? You don't say what your problem is in this message and I search this whole topic and this is your only post. Again sorry for not understanding... -Aalst
×
×
  • Create New...