Closed (fixed)
Project:
Quick Tabs
Version:
5.x-1.3
Component:
User interface
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 May 2008 at 22:53 UTC
Updated:
4 Sep 2008 at 01:52 UTC
Jump to comment: Most recent
Comments
Comment #1
amnion commentedI just tried installing the dev version and I still get the same result. I am never taken to the blocks page to continue making Quick Tabs.
Comment #2
katbailey commentedHi amnion,
that sounds very strange, I haven't come across it before. If you can provide any other information about your Drupal install and browser and whether you are experiencing problems with any other modules, that would help me try to understand what's going on.
regards,
Katherine
Comment #3
amnion commentedI'm using Drupal 5.7 and have tried administering my site through several different computers (thought it could be due to connection speed, etc.) and have tried it with Mozilla and IE7. It does the same thing consistently. The only other problem I'm having with any modules is there is an Account_Reminder that is installed but I cannot get it to show up in Site Configuration (it shows up everywhere else). Here is all the info on that http://drupal.org/node/263926
Comment #4
amnion commentedI also just tried uninstalling and reinstalling and now I can't get the tables to load into the database again:
user warning: Table 'fatalfit_drupal.quicktabs' doesn't exist query: SELECT * FROM quicktabs in /home/fatalfit/public_html/includes/database.mysql.inc on line 172.
Comment #5
Anonymous (not verified) commentedYeah, I was using the version 5.x.1.2 and when I made update for 5.x.1.3, quick tabs had stopped to function and I do not obtain to create more because when i click submit, the page make a refresh and nothing more happens =(
Comment #6
toma commentedSame problem here when update from quicktabs 5.x.1.2 to 5.x.1.3
Comment #7
egouleau commentedI'm on drupal 5.7 and i downloaded and installed the latest version 5.x.1.3 and i can't make this module working...
i did not have the previous version installed but i got the same problem as the others: click on submit does nothing
Comment #8
katbailey commentedHi All,
there shouldn't be any issue with updating from 1.2 to 1.3 but this problem has me stumped. Does anyone have a site where I can see the problem in action?
thanks,
Katherine
Comment #9
amnion commentedHey, I found out my problem was that I wasn't using my user 1, I was using another account with admin privileges. Now it works perfectly.
Comment #10
egouleau commented@katbailey : i'm sorry i can't show you cause i'm under confidential matters...
@amnion : do you mean that admin can't add/configure QTBlocks but standard user can?
Comment #11
lpt6 commentedme 2
cannot create new block using 1.3
Comment #12
amnion commentedegouleau--no, I mean I was using a standard user with special access privileges (same as admin) but it didn't work until I logged in as admin (user 1).
Comment #13
lpt6 commentedI logged in as admin but still cannot make new tab
Comment #14
egouleau commented@amnion : glad it works for you, but i'm logged as admin since the beginning and it doesn't work for me :/
Comment #15
Skys0 commentedHello,
I have the same problem, I have downloaded and installed the latest version (5.x.1.3) and this is not working...
Tested in Firefox 3 and Safari.
Comment #16
drupalina commentedI have the same problem ever since I installed the latest 1.3 version. Can't create or edit new QuickTabs.
I reverted back to 1.2 and everything works as it should.
I'd say 1.3 is an extremely unstable version. 1.2 is the stable version.
More info: I use Drupal 5.7, JQuery Update 5.x-10. These problems occur in IE6 and FF3 (I don't have other browsers)
Comment #17
Matthieu commentedI had exactly the same problem with version 1.3 and Drupal 5.7.
I moved to version 1.2 and it works fine.
Comment #18
alippai commentedThis is a bug report...
Comment #19
katbailey commentedHi All,
I've been on vacation the last couple of weeks, hence the lack of response. This is a high priority for me now though I have still not been able to reproduce the problem. I suspect that not all of the above comments relate to exactly the same problem as in some cases it sounds like an access control issue. Also, the original issue was posted as relating to the 5.x-1.2 release though now people are saying they only get the problem with the 1.3 release. Is the problem still characterised by the fact that when you try to submit the Quick Tab creation or edit form nothing happens?
thanks for your patience ;-)
Katherine
Comment #20
lpt6 commentedIn my case, yes, after update to 1.3, cannot create any new tab
Comment #21
egouleau commentedlike lpt6, when i submit a Quick Tab Creation the page is just refreshed and reseted...
Comment #22
katbailey commentedok, I'm going to need help on this one - can somebody please point me to a test site where I can actually see the problem because without being able to reproduce it there's no way I can fix it.
Oh, and just in case, I'm sure it's nothing this simple - but you're definitely clicking the submit button and not the "more tabs" button? ;-)
Also, please clear your Drupal cache and browser cache, just in case...
thanks,
Katherine
Comment #23
MGParisi commentedIt appears to be a loading issue for me... If you click on the tab too quickly it will not work. you will see a # on the URL. Since we are developers chances are we are using big views with pictures and also have cache disabled... Which means the java script is not loading.
Comment #24
MGParisi commentedIn addition if you click it too quickly you get the wonderfull # at the end of the path. That is caused by the script not loading correctly... if you load the reload with that # you will still get the same first default page, but you WILL loose all of the ability to use the script tabs! it seems to work for me sometimes, and others it does not... these are observations, not absolutes! With a 25 teaser list, with images, cache turned off via Web Developer, and a impatient user. All hell breaks loose
My .JS file is 23 in the list! (I run allot of modules so webdeveloper with cache off will take forever to load the .js!
I am certain its because the .JS file isnt loaded when we click on the tab... However most users wont have this problem. Its an issue with a very large site with a ton of JS files beign loaded and none of them being cached! I simply can not break it with browser cache turned on! I will talk to you in chat kbailey!
Comment #25
thulstrup commentedI think I've found the problem.
It's located in this line in the quicktabs_form_submit function:
if ($form_values['op'] == 'Submit') {The value of $form_values['op'] differs from language to langauge.
For instance on a danish site, the value of $form_values['op'] would be 'Indsend'.
Hope that makes sense to you.
Comment #26
katbailey commentedAaahh - yes! This could be it! I received an email from jaxxed about localisation and how I wasn't passing the 'submit' value through the t() function - it never clicked with me that it could be the root of this problem. And I was very slow getting around to doing it. But I have committed it now. Next dev snapshot will include this fix, ready for your testing ;-)
Comment #27
MGParisi commentedcan you also allow for paging? I believe it is just one variable?!?
Comment #28
katbailey commented@MGParisi - this is unrelated to the issue. You can add a new feature request for this if you like but in the D5 version this can't happen until the larger feature of specifying the active tab has been added. Paging in Views 1.0 means a page refresh - it would default back to the first tab being active. Also, the page number in the url would apply to all Views in all tabs. If someone can suggest a way around that I'll consider it ;-)
Comment #29
MGParisi commentedI am sorry, you are right it is a feature request...
I wanted to tell you I do appreciate your support and code. I wish you were on IRC so I could thank you there.
Comment #30
Anonymous (not verified) commentedYou're RIGHT =D Thanks a lot
Works with me.
Comment #31
Ole Martin commentedI changed "if ($form_values['op'] == 'Submit')" to "if ($form_values['op'] == 'Lagre')" and then it works for me. I,m from Norway and we use "Lagre" (or "send") for "Submit" .
And in the same time, thanks for a great module.
Comment #32
katbailey commentedThis is fixed in the new 1.4 release
Comment #33
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.