Jump to content

Harald Ponce de Leon

  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by Harald Ponce de Leon

  1. Can you please post a copy of your 'alias' file (I'm not even sure if that's it's name or if it has an extension) so those of us who use cPanel and sendmail are able to copy your process.




    help: "|/usr/bin/php -q /home/projects/osCommerce/cvs/catalog/extras/helpdesk/osc_mail2db.php config=/home/projects/osCommerce/cvs/admin/admin/includes/local/configure.php


    All on one line.


    The "help" user does not have to have a user account on the server - it's just an alias.


    Note: Don't forget to run "newaliases" to generate a new aliases.db file :) (should be located in the same directory as the "aliases" file)


    Am I correct in my thinking that we can just change a few minor things in your file and upload it to our usretc directory and all will be working?


    No - as mentioned, configuration is server specific.


    You can try, but don't blame me if something breaks :D

  2. Here is my example at Pair:




    The option to choose above is "Filter"




    In the Mail Sent To field I would enter the mail alias entry of help, sales, info, or whatever so that the helpdesk department email address would be help _AT_ oscommerce.com, sales _AT_ oscommerce.com, info _AT_ oscommerce.com, or whatever.


    [the " _AT_ " string is ofcourse the @ symbol to avoid the forum creating automatic links to non existing email accounts]


    The Pass To field would contain the following:


    /usr/bin/php -q /path/to/osc_mail2db.php config=/path/to/admin/includes/configure.php


    Note: There is no need to enter the | here (as in "|/usr/bin/php -q ....") as this is a html based interface to the mail setup which does the magic automatically behind the scenes.




    The correct term for mail alias entry is indeed Recipe.

  3. There is a reason why little documentation was provided with the contribution in regard to accepting incoming mails - this is very server specific and will be impossible to cover all areas. That is why when people have this working they should report back on the steps they made not only to help others out, but to also put some documentation together. I've put my bit in with the Sendmail example - that is all I did and it works for me.


    I will mention three types of servers:


    1) Localhost (Linux. Windows probably needs a third party application).

    2) Shared Server (little control over the server)

    3) Dedicated Server (some control over the server)


    1) It's more than likely you have no idea what to do otherwise you would not be reading up to this page on this thread :D (smile, sooner or later you will get it working)


    The most important thing to do is to get mails working with your localhost server. I have Gentoo Linux installed, the appropriate documentation for this can be found here:




    If your server documentation is still alien to you, the only suggestion I have is to test this on the shared/dedicated server and let the server administrator take care of it for you.


    2) Ask your server administrator! Tell them you need a mail alias entry to parse a script - provide the examples given in the contribution installation text.


    If your server administrator does not know or has to do research on it, I'd suggest to move to another server hosting company. Hey, this is e-commerce, it should be taken seriously - your server administrator should have the know-how for their own servers!


    3) A combination of 1) and 2).




    I hope that helps somewhat - I am not a unix mail guru so I cannot provide more tips.




    The contribution will also work without a mail alias entry, but then incoming emails cannot be tracked and stored in the database. I think the Contact Us page provided needs to be updated in this case as it needs to store the submited information directly in the database instead of emailing it to the mail alias entry (which would not exist).

  4. What are the downfalls of using gZip? (This seems too good to be true!)

    Am I just sacrificing CPU time, or will I run into compatibility problems with client browsers?


    Remember that it is just the HTML being compressed, not the images. The images are already compressed in either GIF or JPG or whatever.


    I have proposed a php/gzip feature internally and will spruce it up and contribute it soon.


    There is some logic to enable gzip compression only if the client supports it.


    Here are some rough benchmarks:



    Uncompressed length: 27774

    Compressed length: 3753



    Uncompressed length: 25908

    Compressed length: 4045



    Uncompressed length: 25617

    Compressed length: 3428

  5. NOTE: The osc_mail2db.php script has been updated which fixed 2 errors. It can be downloaded in the Contribution package-set at the following link.




    A helpdesk add-on for osCommerce that has the capability to keep track of communication via emails.


    The thread of communication is stored in the database where a ticket number is assigned to a thread.


    It is possible to create template responses which can be used when replying to a ticket entry.


    Departments are setup to handle different areas of communication (help, sales, information, etc).


    [This is a separate work to other helpdesk feature contributions currently available]





  6. This posting is a short description on how contributions should be made. It will be added to the Contributions section when the "adding" pages have been updated to be a little more user friendly.


    When a new contribution is made available, a package is created that holds the description and file. This file can be seen as v1.0 of the contribution made.


    When an updated contribution is made available, it should be added to the original package. This allows different versions of the contribution to exist in an easy to find package.


    Clicking on "Contribute A New Package" will enter a new package into the contributions list. Clicking on "Add A File To This Package" will add a file to an existing package.


    Both methods will show the package on the Newest Contributions list as it has been the latest package to be modified.


    Since a package can hold multiple files, it is a good idea to enter a clear title for new packages without the version number. For example, if an updated categories box is to be contributed, the ideal package name would be Different Style Categories Box instead of My Categories Box v1.0.


    Additional files to this package should include the version number in their title, as the title to the files are shown when viewing the package.

  7. Was this discussed already?  Was it moved for aesthetic or functional reasons when the new checkout process was implemented?


    When Ian's Credit Class work is integrated into the project, there would have been too much information shown to the customer on this one page.


    Originally the textarea box was moved to the Checkout Confirmation page however due to the flexibility of the modules, depending on which module is installed and used the information could have been lost if the form on the confirmation page was sent to the payment processor server.


    It is possible to have the textarea box on the Confirmation page however the modules requiring to make a request to another server via HTTPS POST would need to be done via Curl or using native SSL features in the upcoming PHP 4.3 release - something which would have broken compatibility between servers.


    This is why it was moved to the Checkout Success page.


    By using Curl, the form method on the confirmation page would be taken to the processing page (checkout_process.php) where the request to the payment processor would be done in the before_process() payment class method.

  8. I know it will be really difficult on start . But in 6 moths time we can estabilish an international auction. As we  have whats somany starters dont have a community. As i mentioned before i will be able to supply required webspace , bandwidth, unlimited email accounts etc. But i can not go along with it alone.


    Sure you can - sign up an account at SourceForge and get your solution listed at HotScripts. Thats how I started :)


    I don't know the intentions of your solution on how it will relate to osCommerce - if it no longer relates to osCommerce I will kindly ask you to stop making postings here as this is a support forum for osCommerce only.


    There are plenty of other forum sites available if all you're looking for is help to get you started in your own ways.

  9. This is an interesting quote from their FAQ:


    The menu is free for Non-Profit, Educational & Personal websites as well as incorporating into Open Source Projects. However, you must inform us of your intentions with your URL and number of users, if applicable and we will grant you with a free license and permission to use.


    This is also interesting:


    Why is the DHTML menu no longer free?


    The DHTML Menu was issued to everyone that was prepared to download it and could use it on their website free of charge as long as certain criteria were met.


    However, a vast number of users started to remove copyright notices and did not place links on their site back to our site which was part of the free menu deal.


    Some of them then had problems with the menu and subsequently asked for help even though they were clearly in breach of our terms.


    Some users also DEMANDED that we help them solve their problems as they had spent time incorporating the menu and they dictated that it was their right to use our code.


    .. now if that was set here, how many posts would that reduce the forums to? ;)

  10. Something that we've started to do in the project is to make sure the bells and whistles (javascript) still work when the browser does not support it.


    I think the only example I can provide is the product image in the product information page.


    Clicking on it with javascript enabled will bring up the picture in a new window. Clicking on it with javascript disabled will load a new page with just the image showing.


    This can be done by specifying logic in <noscript></noscript> tags and be writing the javascript logic in javascript itself (huh? I mean with document.write :))


    I do not mind DHTML menus etc - as long as the feature they are representing works with browsers that have it disabled.


    An example here is a DHTML menu - the buttons representing the menus should still be clickable to go to that area so that browsers that do not show the menu can still navigate on your site.


    This isnt a case for dropping bells and whistles - but making sure your site can be navigated by as much browsers as possible - which is important for an online shop otherwise potential customers will be that no more.