Jump to content

halfman

Members
  • Posts

    61
  • Joined

  • Last visited

    Never

Contact Methods

  • Website URL
    http://www.epicdesign.com.au
  • Yahoo
    halfman58

Profile Information

  • Gender
    Male
  • Location
    Australia

halfman's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. have you run anyother website on your MAMP? MAMP runs a different scan for mysql and if the port 8888, and 8889 used by different program then you need to change the ports for you MAMP. Check your MAMP in the preferences and see what is the ports for your apache. go to MAMP website and download the user manual, you can find more info about the ports in there. Hooroo
  2. Mate just google it, or let me know what is you problem I might be able to find you exactly what you want.
  3. I agree with this suggestion, I always use session, they are more secure and easy to use.
  4. I think you need to escape it just because the JTable::store() is binding the post record to the ones in the table and if there are similar then it will update the table. so I would say in the POST you escape the POST array and then use the JTable::store().
  5. Mate I made you a short tutorial, and I have put it on this address Customise Your Template To Use In Joomla it is just a nightly written so I do apologise for any grammar mistake, I will ask my copywriter to look at it. Just let me know if you have any other probelm. Hooroo
  6. What do you exactly want to know about Joomla templates? let me know, I can give you some good tutorials and pdfs
  7. I love Chrome and I use it for browsing but I use FF for web development. Guys I think having IE6 is kind of good because of the challenges. I know by saying that I make so many enemies. I dont mind IE7 or IE8.
  8. instead of die() user trigger_error(mysql_error(), E_USER_ERROR) and see what error are you getting. it is just the first step then we can work on the rest
  9. Mate this code is wrong you wont be able to update a recored and have it as the where condition, it is not very clever of coding and I dont think it is logicly possible. "UPDATE smail SET estimatedDelivery = '".$date."' WHERE estimatedDelivery = '".$id."'"; Needs to be: "UPDATE smail SET estimatedDelivery = '".$date."' WHERE `id` = '".$id."'";
  10. I suuggest killing the script when it has only one event in and see which block of your code dump the error. That is what I will do when I get error in my joomla component, I will go to the component folder and start following the logic of the code and killing the code in each block to find out where the error is triggered, then if I cant find the solution I will try to get help, as I get help very fast because I can pin point exactly which block of code has problem.
  11. No worries mate. Any time, Let me know if you needed any more help. Cheers
  12. Have you installed your joomla directly from your server or your transfer it across and change the config? If you transfer the joomla across then I would suggest go and check the config file. Give me the your component download link, I go and see if there is any reference to the host. it could be looking for your local machine http://localhost instead of your domain name.
  13. Mate, I dont know the structure of your table so I assume that you need some kind of the WHERE condition. I thought if you pass the id from each post you know exactly each post belongs to where in your database (Instead of using a hidden file to pass the id), so the $key is the actual passed id from your FORM, you can use it to point each record properly in its place. for example: UPDATE tableName SET estimatedDelivery = '".$val."' WHERE id = '".$id."' PHP takes care of the array and the value as the array structures will get in place in the order of the submission. for example : [1] => ['10-10-09'] [id] => ['estimatedDelivery'] Have a read on the PHP Array in php.net it will help you a lot.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.