Closed (fixed)
Project:
Flux Slider
Version:
7.x-1.4
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Jan 2013 at 12:25 UTC
Updated:
7 Jan 2013 at 08:44 UTC
Thank you for having updated this module to 1.4 version.
I have set Flux slider Options like what is in the joined screen capture.
Unfortunately, none of the choosed options are actually active on my displayed slideshow.
I have got exactly what is displayed on your http://d7dev.junglecreative.com/ site.
No caption, no controls, no pagination, nothing else appears as expected whatever I set in the options.
Only "Delay between transitions" works correctly.
This is still and unfortunately an unfinished module.
I hope it will be able to work as expected soon since I would really like to integrate it on my own website. Nice job.
| Comment | File | Size | Author |
|---|---|---|---|
| Flux-Slider_issue.png | 24.41 KB | Gyver06 |
Comments
Comment #1
raynimmo commentedNot at my desktop right now but I think I know what is happening here, I think that the admin panel is pulling in the settings from the field labels, where, in english it would be on/off and show/hide and with some boolean values for others. It may be possible that your non-english wordings are what is being set within the database hence when reading them back out when building the block it isnt recognising them and is failing.
If you could help me out by doing a tester with your site set to english and then resave the admin forms and let me know the results.
I would either have to translate when saving or reading from the database or have everything set as boolean values.
If you could get back to me on this as soon as you can and i will push an update this evening.
Comment #2
raynimmo commentedyour screenshot has also shown me that i am not passing the option headers through the translation function either, will amend that this evening also, cheers :-)
Comment #3
Gyver06 commentedYou are absolutely right. After reverting back my drupal site to english as source language, everything is working again.
After reverting from french to english, and opening the configuration options panel, I got this message :
Warning: file_get_contents(/sites/all/libraries/flux-slider/flux.js) [function.file-get-contents]: failed to open stream: No such file or directory in _locale_parse_js_file() (line 1488 of /home/monrtier/public_html/includes/locale.inc). Backtrace:
file_get_contents('/sites/all/libraries/flux-slider/flux.js') locale.inc:1488
_locale_parse_js_file('/sites/all/libraries/flux-slider/flux.js') locale.module:881
locale_js_alter(Array, NULL, NULL) module.inc:1056
drupal_alter('js', Array) common.inc:4232
drupal_get_js('footer') theme.inc:2602
template_process_html(Array, 'html') theme.inc:1106
theme('html', Array) common.inc:5857
drupal_render(Array) common.inc:5704
drupal_render_page(Array) common.inc:2656
drupal_deliver_html_page(Array) boost.module:1393
boost_deliver_html_page(Array) common.inc:2544
drupal_deliver_page(Array, '') menu.inc:532
menu_execute_active_handler() index.php:24
That is strange since I checked the file flux.js already exist at the right place. I have copied (not moved) it from its original installation folder (ie /libraries/flux-slider/js) to the root /libraries/flux-slider.
If I still can be of any help, let me know.
best regards and a happy new year. :-)
Comment #4
raynimmo commentedThanks for that but you maybe should have started this in a separate thread.
I have just finished the most recent code revision for which I had to install the Locale module and the Localization Update module and converted my test environment to French to ensure that the module would perform on multilingual sites. I actually came across that exact same error during my testing.
I think it must be something to do with the Locale module, in particular the private function
_locale_parse_js_file()as that is where the error is pointing. Much like yourself I knew the Flux.js file was present in that location. This error only appears when you change language and then it is gone on the next page refresh.Searching about this, it certainly does seem to be a bug within the Locale module although most of the issues I have found are across a wide range of modules. Most of them seem to get closed after a number of weeks after no activity or follow ups, no doubt due to it fixing itself after a page refresh.
See:
Enabling of core Local module returns no such file errors. > http://drupal.org/node/1022242
Java Script error? > http://drupal.org/node/1714102
Slider does not slide > http://drupal.org/node/1797948
Warning: file_get_contents().... line 1488 > http://drupal.org/node/1826512
Warning: file_get_contents() failed ... _locale_parse_js_file() > http://drupal.org/node/1412476
These are just a few of them, there are many more.
I did come across something interesting in the core issue queue though where a patch has been rolled but it seems like it is still waiting for review. see http://drupal.org/node/1803330
RE: this original thread: translation bug fix on its way :)
Comment #5
raynimmo commentedHave just pushed the latest 7.x-1.5 release onto the repository.
It deals with all of the localization problems and addresses a few other interface tweaks with regards to the module administration panel.
Previous versions where the height was an issue and a quick fix was applied seems to have removed from view the pagination controls when they are selected to be shown. Have taken into account their selection now when setting the overall slider containers height.
The latest version contains a database upgrade, please make sure to run it as it will remove any language settings such as on/off from the database variables and replace them with Boolean values.
Comment #6
Gyver06 commentedI didn't open a new thread since I thought this "No such file or directory" error was related to your module. Which is not the case in fact, sorry for that.
The last link http://drupal.org/node/1803330 did it perfectly.
I tested it and the error is no more displayed.
Many thanks for your very appreciated help on this issues.
Comment #7
raynimmo commented