Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #13637

    Hey Guys,

    I need to update the theme files before I switch over to WP 3.4, but the update log in the version_shoutbox.rtf is a bit vague.

    I’ve customised a lot of the files in the theme so I need to know exactly which files Kriesi has changed in the updates.

    For example in the 1.15 update there is a change listed as:

    folder: framework/php/avia_shortcodes – updated security for shortcode files

    But in the avia_shortcodes folder there are 4 more subfolders and two .php files. Which of these elements has been changed?

    The same for the 1.16 update. There is a change listed as:

    folder: framework – update to the latest version

    But the framework folder has 4 subfolders and a .php file in it. So what has been updated exactly?

    Please can you make the update logs more precise in future?

    Thanks

    rich

    #79968

    This piece of code from the updated (1.16) shoutbox/framework/php/function-set-avia-frontend.php file:

    if(!$avia_post_id)

    {

    $avia_post_id = @get_the_ID();

    }

    Is that “@” supposed to be there?

    #79969

    1) I’ll ask Kriesi if he can remember which files received an update. Probably he can’t remember which files were updated though. You can use tools like Beyond compare and/or Notepad++ to compare files.

    2) Yes, the @ tells php to execute a function without dropping error messages or warnings. This is very useful if the developer isn’t sure if a function can be executed or not. I.e. the @ is very important for file operations because strict file permissions can cause errors and the @ allows you to test if a file manipulation function works correctly or not – if not you can output a message like “please change the permissions to 777″, etc.).

Viewing 3 posts - 1 through 3 (of 3 total)

The topic ‘UPDATE confusion’ is closed to new replies.