You are here

CHANGELOG.txt in SWF Tools 6

Same filename and directory in other branches
  1. 5 CHANGELOG.txt
  2. 6.3 CHANGELOG.txt
  3. 6.2 CHANGELOG.txt
12 February 2009
----------------
#371735 - Fixed - incorrect construction of id tag in HTML.
#371615 by KarenS - fix lines that result in PHP errors when parameters are
not defined.

07 October 2008
---------------
#308515 - Fixed - string used for determining extension was empty when a remote
file is being checked, so code changed to check a more appropriate string.

06 October 2008
---------------
Appending the nocache string to filenames seems to have broken content, but
I'm sure it was working before. Recommitting without the cache setting until
I can be sure it is working right.
#308515 - Not fixed the root cause in the auto-detection routine, but fixed
another bug that prevented the user specifying a specific player to over-ride
autodetection. This allows the symptoms of #308515 to be masked.

03 October 2008
---------------
#314045 - Constants incorrectly defined - fixed.

23 September 2008
-----------------
Cumulative changes that address a number of issues.
Identification of default players on the admin screen was wrong.
swftools_get_media_url changed due to bug that resulted in double /
appearing in the file path (#308172).
Auto-detection of sizes changed so that players are always auto
detected even when a remote media url is configured.
Test content added to status page to help identify if SWF Tools is
working.
Missing php from <?php in swftools.admin.status.inc

6 September 2008
----------------
First official release of SWF Tools for Drupal 6!

Text below describes what was changed as part of this release compared to v5.

swftools.module
---------------
Menus updated to v6
Use of l() in filter fixed
Settings call backs updated
File checks in swf() modified to better handle local files(?)
_swftools_tf logic modified - was returning wrong values
allowfullscreen parameter added to _swftools_params and embedding generation routine
Text changed to sentence case for consistency with rest of Drupal
Assigning action in swf() occurred twice - one instance deleted
$nocache logic changed so caching string only appended once at the very end (not sure how this works)
swftools_get_media_url changed to use file_create_url - should allow private file system
Suggested fix for encoding in _swftools_get_flashvars_string applied
swftools_theme() added to allow theme function to be registered
Code that attempts to generate a valid base path altered to make a better guess
Base path made compatible with private file system
Fixes as per issue list at end of this document
Parameter list extended to better support macros
SWF Filter changed to be easier to use with other filters (<swf > is replaced
by [swf ] during the prepare phase, so the code isn't stripped by HTML filters.
[swf ] can be used directly when writing a filter. Filters can now be written
using just [swf file=""] or [swf files=""] and filter will use file/files to
determine if a playlist is intended. [swflist ] can still be used so old filter
entries will work as originally planned.
Filter amended to strip <p></p> from around the filter, to allow W3C validation
to pass.
Direct embedding mark-up changed to be standards compliant.
swf() function parameters altered - now works more like the rest of Drupal 6 as
an array of parameters is passed, rather than a series of parameters - pass an
array with (optional) keys params, flashvars, othervars, methods. Params are
passed to the generation code, flashvars becomes the flashvars string,
othervars and method are passed to SWF Tools handlers.
Check for existence of playlist directory (and creation as required) added to
swftools_get_playlist_path() so it is created without having to visit settings
page.
Constant SWFTOOLS_INSTALLED added to make it easier to notify other modules if
SWF Tools is available.
Adding js to every page now defaults to TRUE (and SWFTOOLS_ALWAYS_ADD_JS added
as a constant for code legibility). This means that SWF Tools behaves as
"expected" with filters, without users having to specifically set this option.
More descriptive messages when no player is configured, so users are directed
to the appropriate settings page.
Various drupal_set_messages made translate by use of t() function.
Wording of settings pages changed to make more consistent with rest of Drupal.
When playing media file_url is added to othervars['file_url'] so that player
modules can access the media file path if they need to. This is particularly
required for FlowPlayer to allow the appropriate config string to be built.
swftools_push_js() added to hook_init(), rather than hook_menu() since it is
technically not a menu function!
New code added to direct embedding to assign an object id to the outer (IE6)
object - without this JW Media Player 4 with IE6 causes pages to say they have
an error.


swftools.admin.inc
------------------
Form creation code adjusted to suit v6 menu call back
Allow full screen parameter added to embed form
Missing files now generate a download link if the download key is set in the
methods array.
Settings page altered slightly to put all file handling options together (some
were under embedding settings). Means embedding settings is now simple for new
users.
Settings moved to sit under Administer > Site configuration > SWF Tools rather
than promoting SWF Tools to a top level below Administer.
Option added to file handling to allow SWF Tools to respond to requests to
access swf, jpg, jpeg, mp3, flv and xml under a private file system.
Cache flushing now calls drupal_flush_all_caches() which clears filters, block
and page caches, so is more likely to ensure changes to flash content are
properly rendered later.


swftools.admin.status.inc
-------------------------
Added a status page that generates reports much like the system status report.
Intent is to provide some diagnostics if an installation isn't working.
At the moment it can report on whether the embedding and playback features
appear to be correctly configured (methods are available, supporting files are
available etc)
Status report is found at admin/reports/swftools.


genericplayers.module
---------------------
Menu updated to v6
Option to disable autoplay flv disabled as generic player always autoplays.


swfobject.info
--------------
Modified to v6


swftools.info
-------------
Modified to v6


swfobject.module
----------------
Added a download key to swfobject_swftools_methods() so the admin form can
provide a link to the required files


onepixelout.module
---------------
Menu updated to v6
Added a download key to onepixelout_swftools_methods() so the admin form
can provide a link to the required files
_swf() and _swflist() functions removed as redundant


wijering.info
-------------
Name string renamed JW Media Player 3 to make explicit to version 4 module.
Description string changed to make explicit this is for JW Player 3.


wijering.module
---------------
Menu updated to v6
Added a download key to wijering_swftools_methods() so the admin form can
provide a link to the required files
_swf() and _swflist() functions removed as redundant


wijering.admin.inc
------------------
wijering_admin_form_submit updated to forms API v6
Form routine tweaked to make it look more like a regular system settings form,
ie Reset to default option added to admin form
Confirmation message added to simulate settings form


wijering4.module / wijering4.admin.inc / wijering4.info
-------------------------------------------------------
Initial version of a module to support Wijering media player 4.
Some of the parameters have been renamed, some are gone, and some new ones
have been implemented.


imagerotator.module / imagerotator.admin.in / imagerotator.info
---------------------------------------------------------------
Image rotator separated out from JW Media Player 3 - logically this is a
different module to the main player module, so it seems sensible to
have this as a separate package. To the end user it makes a logical
distinction between media players and the image cycler. Also, the JW
Image Rotator is still at version 3, so to have Media Player 4 and
Image Rotator 3 would mean enabling Media Player 3 which is counter
intuitive! Internally it still uses the name WIJERING_IMAGEROTATOR
so the existing variables are preserved, even though this is now a
distinct module.


lutman.module
-------------
Added download key to methods array to allow easy download.


lutman.info
-----------
Updated to v6
Is descriptor right? It says lutman is included, but it isn't?


ufo.module
-------------
Added download key to methods array to allow easy download.
Removed alert pop-ups.


ufo.info
-----------
Updated to v6


simpleviewer.module
-------------------
Menu updated to v6.


swfobject2.module / swfobject2.info
-----------------------------------
Support for SWF Object 2 added, and output made standards compliant.
Uses the flashvars in array format, rather than string form, to provide
clearer javascript, and seems to be working ok.
Original version of this module added the js to the page header, but
that causes content generated with filters to break!
js now added to page body, rather than header - remembered that when filter
caching is enabled the js won't get added to the page header!
New code added to assign unique id to the object (using swf followed by the
same id numbers as the div. Without this JW Media Player 4 with IE6 causes
pages to say they have an error.


flowplayer.module / flowplayer.info / flowplayer.admin.inc
----------------------------------------------------------
Feature request under SWF Tools 5.1 asked for support for FlowPlayer.
This module introduces initial support, but more work needed at the
moment. Adding this module resulted in the changes to swfobject2 to
use the array format, and the addition of the media file path to
the resolved_methods array in SWF Tools itself.


Private file handling
---------------------
Change to method of generating path seems to allow private files to work.
Tested with playback of a swf, and also an mp3 via generic and Wijering players.
If files are placed on the site via FTP then a SWF Tools option must be set
on the File handling page to allow SWF Tools to grant access to media files.
It allows access to swf, mp3, flv, xml, jpg, jpeg and png formats. If access is
denied by any other module then access is not allowed, so content that is
being protected by a module is not compromised by activating this setting.
The default setting for allowing access to private files is OFF, so to let
SWF Tools allow handling of private files it must be explicitly set by the
user on the settings page (Administer > Site configuration > SWF Tools >
File handling > Private file system).


General
-------
Broken identifier strings replaced with correct format
UFO and SWFObject 1.5 are both superceded by SWFObject 2.0 - new module written
but not tested extensively yet.
Configuration pages moved to sit under Administer > Site configuration > SWF
Tools, rather than having SWF Tools promoted to its own level.
Default HTML alt added as a constant for clarity, and wording made a little
more informative to assist users who don't see the content.
File locations settings moved from embedding page to file handling page. This
is more consistent, and presents new users with fewer options on the first
settings page. Most people probably never change anything other than the
embedding method at first.


Issue queue
-----------
218326 - Full screen does not work
166804 - Fullscreen option for JW PLAYER
153780 - Full Screen Support using Wijering Flash
Full screen now a parameter on the settings page, and passed to flash modules
to enable it.

191279 - Strange escaping behaviour of ":" and "/" and 1 pixel out Player
173021 - 1PixelOut - Error Opening File
154364 - input formats!
202591 - 1pixelout can't find file
Incorporated the suggested fix to reverse the encoding.
This probably explains "203301 - Error Opening File" as well.

178283 - Patch to fix bug in "base" parameter for direct embedding
Patch applied - base now properly set when using direct embedding mode.

179322 - variable_get for Flash Version incorrect
Suggested fix applied.
scale and swliveconnect had similar errors so fixed those too.

146935 - Menu titles get strange formatting because of surplus white space
Fixed

157397 - file path for attachment is wrong
Think this is fixed with modified file handling mechanism that was needed as
the "double files" issue occurred with flash node too.

252956 - Private Uploads and SWFTools
Should be fixed with new code that allows used of private file systems with
SWF Tools. Note - SWF Tools must be allowed to grant access to playlists.

294163 - Standards Compliant Flash
SWF Tools now produces standards complaint (XHTML 1.0 Strict) using either
direct embedding or via SWF Object 2 *in most cases*. The filter component
has been updated to string the <p></p> that wrap around the <div> containing
the flash, but if you use the format in the middle of a paragraph this won't
work properly and you will get code that FAILS validation. If validation is
important then you may need to test pages containing to SWF Tools content to
verify that they are validating properly.

181473 - FlowPlayer support
FlowPlayer support has been added.

233375 - Upgrade to 6.0
Here it is!

186896 - Wijering player w/playlist shows up on IE, not on FF or Opera
Have not been able to recreate this error, but seems to be ok under all tests
during develop of SWF Tools 6, so assuming can be closed.


File

CHANGELOG.txt
View source
  1. 12 February 2009
  2. ----------------
  3. #371735 - Fixed - incorrect construction of id tag in HTML.
  4. #371615 by KarenS - fix lines that result in PHP errors when parameters are
  5. not defined.
  6. 07 October 2008
  7. ---------------
  8. #308515 - Fixed - string used for determining extension was empty when a remote
  9. file is being checked, so code changed to check a more appropriate string.
  10. 06 October 2008
  11. ---------------
  12. Appending the nocache string to filenames seems to have broken content, but
  13. I'm sure it was working before. Recommitting without the cache setting until
  14. I can be sure it is working right.
  15. #308515 - Not fixed the root cause in the auto-detection routine, but fixed
  16. another bug that prevented the user specifying a specific player to over-ride
  17. autodetection. This allows the symptoms of #308515 to be masked.
  18. 03 October 2008
  19. ---------------
  20. #314045 - Constants incorrectly defined - fixed.
  21. 23 September 2008
  22. -----------------
  23. Cumulative changes that address a number of issues.
  24. Identification of default players on the admin screen was wrong.
  25. swftools_get_media_url changed due to bug that resulted in double /
  26. appearing in the file path (#308172).
  27. Auto-detection of sizes changed so that players are always auto
  28. detected even when a remote media url is configured.
  29. Test content added to status page to help identify if SWF Tools is
  30. working.
  31. Missing php from
  32. 6 September 2008
  33. ----------------
  34. First official release of SWF Tools for Drupal 6!
  35. Text below describes what was changed as part of this release compared to v5.
  36. swftools.module
  37. ---------------
  38. Menus updated to v6
  39. Use of l() in filter fixed
  40. Settings call backs updated
  41. File checks in swf() modified to better handle local files(?)
  42. _swftools_tf logic modified - was returning wrong values
  43. allowfullscreen parameter added to _swftools_params and embedding generation routine
  44. Text changed to sentence case for consistency with rest of Drupal
  45. Assigning action in swf() occurred twice - one instance deleted
  46. $nocache logic changed so caching string only appended once at the very end (not sure how this works)
  47. swftools_get_media_url changed to use file_create_url - should allow private file system
  48. Suggested fix for encoding in _swftools_get_flashvars_string applied
  49. swftools_theme() added to allow theme function to be registered
  50. Code that attempts to generate a valid base path altered to make a better guess
  51. Base path made compatible with private file system
  52. Fixes as per issue list at end of this document
  53. Parameter list extended to better support macros
  54. SWF Filter changed to be easier to use with other filters ( is replaced
  55. by [swf ] during the prepare phase, so the code isn't stripped by HTML filters.
  56. [swf ] can be used directly when writing a filter. Filters can now be written
  57. using just [swf file=""] or [swf files=""] and filter will use file/files to
  58. determine if a playlist is intended. [swflist ] can still be used so old filter
  59. entries will work as originally planned.
  60. Filter amended to strip

    from around the filter, to allow W3C validation
  61. to pass.
  62. Direct embedding mark-up changed to be standards compliant.
  63. swf() function parameters altered - now works more like the rest of Drupal 6 as
  64. an array of parameters is passed, rather than a series of parameters - pass an
  65. array with (optional) keys params, flashvars, othervars, methods. Params are
  66. passed to the generation code, flashvars becomes the flashvars string,
  67. othervars and method are passed to SWF Tools handlers.
  68. Check for existence of playlist directory (and creation as required) added to
  69. swftools_get_playlist_path() so it is created without having to visit settings
  70. page.
  71. Constant SWFTOOLS_INSTALLED added to make it easier to notify other modules if
  72. SWF Tools is available.
  73. Adding js to every page now defaults to TRUE (and SWFTOOLS_ALWAYS_ADD_JS added
  74. as a constant for code legibility). This means that SWF Tools behaves as
  75. "expected" with filters, without users having to specifically set this option.
  76. More descriptive messages when no player is configured, so users are directed
  77. to the appropriate settings page.
  78. Various drupal_set_messages made translate by use of t() function.
  79. Wording of settings pages changed to make more consistent with rest of Drupal.
  80. When playing media file_url is added to othervars['file_url'] so that player
  81. modules can access the media file path if they need to. This is particularly
  82. required for FlowPlayer to allow the appropriate config string to be built.
  83. swftools_push_js() added to hook_init(), rather than hook_menu() since it is
  84. technically not a menu function!
  85. New code added to direct embedding to assign an object id to the outer (IE6)
  86. object - without this JW Media Player 4 with IE6 causes pages to say they have
  87. an error.
  88. swftools.admin.inc
  89. ------------------
  90. Form creation code adjusted to suit v6 menu call back
  91. Allow full screen parameter added to embed form
  92. Missing files now generate a download link if the download key is set in the
  93. methods array.
  94. Settings page altered slightly to put all file handling options together (some
  95. were under embedding settings). Means embedding settings is now simple for new
  96. users.
  97. Settings moved to sit under Administer > Site configuration > SWF Tools rather
  98. than promoting SWF Tools to a top level below Administer.
  99. Option added to file handling to allow SWF Tools to respond to requests to
  100. access swf, jpg, jpeg, mp3, flv and xml under a private file system.
  101. Cache flushing now calls drupal_flush_all_caches() which clears filters, block
  102. and page caches, so is more likely to ensure changes to flash content are
  103. properly rendered later.
  104. swftools.admin.status.inc
  105. -------------------------
  106. Added a status page that generates reports much like the system status report.
  107. Intent is to provide some diagnostics if an installation isn't working.
  108. At the moment it can report on whether the embedding and playback features
  109. appear to be correctly configured (methods are available, supporting files are
  110. available etc)
  111. Status report is found at admin/reports/swftools.
  112. genericplayers.module
  113. ---------------------
  114. Menu updated to v6
  115. Option to disable autoplay flv disabled as generic player always autoplays.
  116. swfobject.info
  117. --------------
  118. Modified to v6
  119. swftools.info
  120. -------------
  121. Modified to v6
  122. swfobject.module
  123. ----------------
  124. Added a download key to swfobject_swftools_methods() so the admin form can
  125. provide a link to the required files
  126. onepixelout.module
  127. ---------------
  128. Menu updated to v6
  129. Added a download key to onepixelout_swftools_methods() so the admin form
  130. can provide a link to the required files
  131. _swf() and _swflist() functions removed as redundant
  132. wijering.info
  133. -------------
  134. Name string renamed JW Media Player 3 to make explicit to version 4 module.
  135. Description string changed to make explicit this is for JW Player 3.
  136. wijering.module
  137. ---------------
  138. Menu updated to v6
  139. Added a download key to wijering_swftools_methods() so the admin form can
  140. provide a link to the required files
  141. _swf() and _swflist() functions removed as redundant
  142. wijering.admin.inc
  143. ------------------
  144. wijering_admin_form_submit updated to forms API v6
  145. Form routine tweaked to make it look more like a regular system settings form,
  146. ie Reset to default option added to admin form
  147. Confirmation message added to simulate settings form
  148. wijering4.module / wijering4.admin.inc / wijering4.info
  149. -------------------------------------------------------
  150. Initial version of a module to support Wijering media player 4.
  151. Some of the parameters have been renamed, some are gone, and some new ones
  152. have been implemented.
  153. imagerotator.module / imagerotator.admin.in / imagerotator.info
  154. ---------------------------------------------------------------
  155. Image rotator separated out from JW Media Player 3 - logically this is a
  156. different module to the main player module, so it seems sensible to
  157. have this as a separate package. To the end user it makes a logical
  158. distinction between media players and the image cycler. Also, the JW
  159. Image Rotator is still at version 3, so to have Media Player 4 and
  160. Image Rotator 3 would mean enabling Media Player 3 which is counter
  161. intuitive! Internally it still uses the name WIJERING_IMAGEROTATOR
  162. so the existing variables are preserved, even though this is now a
  163. distinct module.
  164. lutman.module
  165. -------------
  166. Added download key to methods array to allow easy download.
  167. lutman.info
  168. -----------
  169. Updated to v6
  170. Is descriptor right? It says lutman is included, but it isn't?
  171. ufo.module
  172. -------------
  173. Added download key to methods array to allow easy download.
  174. Removed alert pop-ups.
  175. ufo.info
  176. -----------
  177. Updated to v6
  178. simpleviewer.module
  179. -------------------
  180. Menu updated to v6.
  181. swfobject2.module / swfobject2.info
  182. -----------------------------------
  183. Support for SWF Object 2 added, and output made standards compliant.
  184. Uses the flashvars in array format, rather than string form, to provide
  185. clearer javascript, and seems to be working ok.
  186. Original version of this module added the js to the page header, but
  187. that causes content generated with filters to break!
  188. js now added to page body, rather than header - remembered that when filter
  189. caching is enabled the js won't get added to the page header!
  190. New code added to assign unique id to the object (using swf followed by the
  191. same id numbers as the div. Without this JW Media Player 4 with IE6 causes
  192. pages to say they have an error.
  193. flowplayer.module / flowplayer.info / flowplayer.admin.inc
  194. ----------------------------------------------------------
  195. Feature request under SWF Tools 5.1 asked for support for FlowPlayer.
  196. This module introduces initial support, but more work needed at the
  197. moment. Adding this module resulted in the changes to swfobject2 to
  198. use the array format, and the addition of the media file path to
  199. the resolved_methods array in SWF Tools itself.
  200. Private file handling
  201. ---------------------
  202. Change to method of generating path seems to allow private files to work.
  203. Tested with playback of a swf, and also an mp3 via generic and Wijering players.
  204. If files are placed on the site via FTP then a SWF Tools option must be set
  205. on the File handling page to allow SWF Tools to grant access to media files.
  206. It allows access to swf, mp3, flv, xml, jpg, jpeg and png formats. If access is
  207. denied by any other module then access is not allowed, so content that is
  208. being protected by a module is not compromised by activating this setting.
  209. The default setting for allowing access to private files is OFF, so to let
  210. SWF Tools allow handling of private files it must be explicitly set by the
  211. user on the settings page (Administer > Site configuration > SWF Tools >
  212. File handling > Private file system).
  213. General
  214. -------
  215. Broken identifier strings replaced with correct format
  216. UFO and SWFObject 1.5 are both superceded by SWFObject 2.0 - new module written
  217. but not tested extensively yet.
  218. Configuration pages moved to sit under Administer > Site configuration > SWF
  219. Tools, rather than having SWF Tools promoted to its own level.
  220. Default HTML alt added as a constant for clarity, and wording made a little
  221. more informative to assist users who don't see the content.
  222. File locations settings moved from embedding page to file handling page. This
  223. is more consistent, and presents new users with fewer options on the first
  224. settings page. Most people probably never change anything other than the
  225. embedding method at first.
  226. Issue queue
  227. -----------
  228. 218326 - Full screen does not work
  229. 166804 - Fullscreen option for JW PLAYER
  230. 153780 - Full Screen Support using Wijering Flash
  231. Full screen now a parameter on the settings page, and passed to flash modules
  232. to enable it.
  233. 191279 - Strange escaping behaviour of ":" and "/" and 1 pixel out Player
  234. 173021 - 1PixelOut - Error Opening File
  235. 154364 - input formats!
  236. 202591 - 1pixelout can't find file
  237. Incorporated the suggested fix to reverse the encoding.
  238. This probably explains "203301 - Error Opening File" as well.
  239. 178283 - Patch to fix bug in "base" parameter for direct embedding
  240. Patch applied - base now properly set when using direct embedding mode.
  241. 179322 - variable_get for Flash Version incorrect
  242. Suggested fix applied.
  243. scale and swliveconnect had similar errors so fixed those too.
  244. 146935 - Menu titles get strange formatting because of surplus white space
  245. Fixed
  246. 157397 - file path for attachment is wrong
  247. Think this is fixed with modified file handling mechanism that was needed as
  248. the "double files" issue occurred with flash node too.
  249. 252956 - Private Uploads and SWFTools
  250. Should be fixed with new code that allows used of private file systems with
  251. SWF Tools. Note - SWF Tools must be allowed to grant access to playlists.
  252. 294163 - Standards Compliant Flash
  253. SWF Tools now produces standards complaint (XHTML 1.0 Strict) using either
  254. direct embedding or via SWF Object 2 *in most cases*. The filter component
  255. has been updated to string the

    that wrap around the
    containing
  256. the flash, but if you use the format in the middle of a paragraph this won't
  257. work properly and you will get code that FAILS validation. If validation is
  258. important then you may need to test pages containing to SWF Tools content to
  259. verify that they are validating properly.
  260. 181473 - FlowPlayer support
  261. FlowPlayer support has been added.
  262. 233375 - Upgrade to 6.0
  263. Here it is!
  264. 186896 - Wijering player w/playlist shows up on IE, not on FF or Opera
  265. Have not been able to recreate this error, but seems to be ok under all tests
  266. during develop of SWF Tools 6, so assuming can be closed.