Looking for programmer for MediaShare Suite script.

Discussion in 'Programming' started by Mackos, Feb 26, 2009.

  1. #1
    Hi !
    I'm looking for programmer who can take care (technical care) for my website which is with script from http://www.mediasharesuite.com/ .
    I'll pay via paypal .
     
    Mackos, Feb 26, 2009 IP
  2. Mackos

    Mackos Well-Known Member

    Messages:
    364
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    130
    As Seller:
    100% - 0
    As Buyer:
    100% - 0
    #2
    I mean to repair it when any errors show up.
     
    Mackos, Feb 26, 2009 IP
  3. ankit_frenz

    ankit_frenz Active Member

    Messages:
    1,111
    Likes Received:
    41
    Best Answers:
    0
    Trophy Points:
    63
    As Seller:
    100% - 0
    As Buyer:
    100% - 0
    #3
    i can help...what error you are getiing>??
     
    ankit_frenz, Feb 26, 2009 IP
  4. Mackos

    Mackos Well-Known Member

    Messages:
    364
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    130
    As Seller:
    100% - 0
    As Buyer:
    100% - 0
    #4
    While I'm uploading file the
    show's up.
    Do you have any experience with this script ?
     
    Mackos, Feb 26, 2009 IP
  5. juliston

    juliston Member

    Messages:
    35
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    41
    As Seller:
    100% - 0
    As Buyer:
    100% - 0
    #5
    Hi,
    Hope this will be helpful.

    Common Cause:

    This warning is often caused by a blank space or extra line at the beginning or end of a .php file.

    Check the error for the filename that generated the error (ie: the "output started at...." filename), open that file in your text editor and remove the extra spaces or lines immediately before the first <?php marks in the file, or after the closing ?>

    Other Causes: Syntax errors

    In the example above, you'll see output started at /....includes/something/something/something.php:12. The includes/something/something/something.php is the filename you need to be concerned about. The :12 means that the problem you need to fix is on line 12.

    In that same example, the /includes/something_else.php on line 67 message can be completely ignored. It is not the problem. It is the one that discovered that the problem had already occurred.

    If the "headers already sent" error appears AFTER any other error, then you need to fix that other error FIRST. (The error message itself is what caused headers to be sent, so fixing that error will cause the second error to go away too.)



    Summary:

    a) look for where it 'started at'
    b) track the line number
    c) check what's normally happening on that line.
    --- If it's the end of the file, then it's blank spaces.
    --- If it's the start of the file, it's likely spaces.
    --- Elsewhere it could be a syntax error or the result of an "echo()" statement which is displaying info or perhaps debug code.
    --- Common syntax errors include the use of single-quotes inside statements that already have single-quotes. Check to be sure your quotes aren't mismatched. If you need to use single-quotes while inside other single-quotes, change yours to \' instead of just '.
    d) the rest of the info simply shows other execution information, mainly the part of the code that discovered that it cannot proceed as expected due to the problem that happened in the 'started at' location.


    You can find many results in google for this error...

    You if still need help, send me the php file. I will check and fix the bug for you :)


    Thanks and Regards
    Juliston.
     
    juliston, Feb 26, 2009 IP