I have added this already but cannot see it so apologies if this is a duplicate.

Repeatable -: Always
OS -: Hosted at Inmotion whatever that OS is, Client is WIN 10
Browser- : Chrome and MS Edge

Steps to repeat:

1. Create more than 37 quiz questions (more than one page full)
2. Open question bank
3. Select any action to advance to the next page (i.e. 2, next or last)

Expected result
- Next page will display

Actual result
- Does not move to next page
- pop-up box with error message (see attachment)

Because the error mentioned Ajax i did the following
1. Checked to see of the Ajax module was enabled (it was not)
2. retested - same error
3. Enabled ajax module
4. retested, same error

I conclude the ajax module was not relevant to the error

Logs -: there were no error messages in any logs that I could find

---end---

CommentFileSizeAuthor
#3 A quiz test Drupal 7 TestField VI.png69.04 KBteeyo
Drupal Quiz Error.png36.43 KBTashko
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

petertashkoff@gmail.com created an issue. See original summary.

Tashko’s picture

Tashko CreditAttribution: Tashko commented

I have found a workaround.
I clicked the gear icon in the view and edited it to display all items.
This avoided the use of the paginator and avoided the problem.

teeyo’s picture

teeyo CreditAttribution: teeyo as a volunteer commented
FileSize
A quiz test Drupal 7 TestField VI.png69.04 KB

Hello petertashkoff@gmail.com,

I tried to replicate the scenario, but I only added like 7 questions (too lazy to add 26 question - because the default pager is set to 25 item per page) and I can't use devel to generate content, there's an error when using PHP 7, anyway, and then I went to admin/structure/views/view/quiz_question_bank/edit to change the default pager to 3 items per page (which will display the pager). I tested out all the pager, it works just fine. I guess the module is not the source of your ajax issue.

Tashko’s picture

Tashko CreditAttribution: Tashko commented

Hi Teeyo - Thanks for checking and yes quite possible something else is affecting it.
I am not sure though that your result is conclusive because, as you point out, you have used a different data set size, and the error may be set-size related.
Again, thanks for taking the time to test.
I am now up to 65 questions in the bank and my workaround is still functioning.
Cheers

djdevin’s picture

djdevin
Location Philadelphia
CreditAttribution: djdevin at Cadmium commented
Status: Active » Closed (cannot reproduce)

We have quiz running with 10,000+ questions and have not seen this issue. It does seem like something else is at play.

If you find out why it is buggy please feel free to reopen.

Tashko’s picture

Tashko CreditAttribution: Tashko commented
Status: Closed (cannot reproduce) » Active

The bug exists and something is causing it. I shouldn't have to fix the bug myself to have the issue open.
OK so it is not the data set size. So it must be something else? Unless you think I am lying. Would you like to see a video?
I am frankly disappointed that in 2017 some people still think 'I personally cannot reproduce your problem' is cause to close it.

djdevin’s picture

djdevin
Location Philadelphia
CreditAttribution: djdevin as a volunteer commented

Project maintainers cannot investigate your specific Drupal set up - e.g. server OS, modules installed, HTTP configuration, PHP version, database type - none of which you have provided. In fact you just provided "whatever OS" which really does not help. Your [Insert year here] is not a good excuse for leaving an issue with lack of information open.

I noticed you are brand new to Drupal.org and this is your first post so please review the issue etiquette: https://www.drupal.org/node/1839650

Especially:

> Don't: Be ungrateful. It can be very frustrating when something doesn't work as you'd hoped but don't take this out on the developer or the Issue Queue.

One good way to help project maintainers is to reproduce the issue on a cleanly installed Drupal 7, with only the module in question installed.

You can also use https://simplytest.me/ to test the module out by itself. If you cannot reproduce it there, it's likely a problem with your configuration or other modules. If you find it not reproducible by itself, try disabling all modules installed on your site one by one until the issue doesn't happen anymore.

Tashko’s picture

Tashko CreditAttribution: Tashko commented

It is a basic tenet of service in IT that the person raising the issue is the only person that can close it.
Please don't preach to me. Your implication that since the service is free I should have to put up with whatever I get is pretty much 1980's thinking. Why should I be grateful that you closed my issue after making a half-baked review of it?

Your response would have been useful if it - to start with - had said something like:

======================================================
I have trialed this on a question set with 10,000 questions so the size alone is not the problem.
I have not checked the code that is being triggered by the issue log, perhaps someone could check that, as it could be a simple setting somewhere.

Also:
One good way to help project maintainers is to reproduce the issue on a cleanly installed Drupal 7, with only the module in question installed. you might want to try that.

You can also use https://simplytest.me/ to test the module out by itself. If you cannot reproduce it there, it's likely a problem with your configuration or other modules. If you find it not reproducible by itself, try disabling all modules installed on your site one by one until the issue doesn't happen anymore.
=====================================================

Now that ^^ would have been useful.

Your actual initial response provided one piece of information that was useful (size) but that benefit was overridden by your assumption that you could close my issue without exhaustive investigation - contrary by the way to service desk etiquette anywhere in the developed world.

Note I am not demanding you do exhaustive investigation I am just requiring you to keep your hands off closing my issue unless you have first done so. That is fair isn't it?

Thank you for making a response that now provides useful information that I can follow up.

if someone has a comment based on the issue log reference to ajax and views that would be useful too.

djdevin’s picture

djdevin
Location Philadelphia
CreditAttribution: djdevin as a volunteer commented

Your first revision of the post before you erased it started with:

Devin I have been in IT for 30 years and your attitude is common among the worst kind of service desk personnel.

- petertashkoff@gmail.com

Nice personal attack there.

We aren't IT service desk personnel, we are developers that have to handle your support inquiries as well, except we also do it for free. You're free to reopen closed issues, but we get so many support issues that if the issue is not reproducible it usually gets closed unless more information becomes available. There are so many configurations and flavors of Drupal distributions that it would take an eternity to personally reproduce everyone's configuration.

Again I suggest reading the Drupal queue etiquette. There is absolutely no reason to get fired up over a closed issue that could not be reproduced by 2 others under the same conditions. It is basic queue maintenance. You easily could have said "I have more information" and we could continue researching. You're also free to fork this project if you don't like me and do it your own way.

I investigated your issue and also mocked up 10,000 questions and could not reproduce. Quiz comes with mock question generation support for issues that are exactly like this so you can do it yourself if you need it to build STR.

Tashko’s picture

Tashko CreditAttribution: Tashko commented

I also said half-arsed and amended it to half-baked.

Thanks for the additional info that you did not as you originally stated have a 10k question quiz, you mocked one up with a generator. So the question of size is still on the table.

Stay off my issue please.

djdevin’s picture

djdevin
Location Philadelphia
CreditAttribution: djdevin as a volunteer commented
Status: Active » Closed (won't fix)

After Googling your error message I found your issue and it's with clean URLs being off or misconfigured. This is a server level issue and not Quiz. I was able to reproduce your issue with Quiz, but also in Views core and in some other modules (Admin views, Media) that have AJAX views. We can't fix it in the project here as it's an issue split between another project and your server configuration.

You have two options:

1. Enable clean URLs
2. Disable the "overlay" module
3. Disable AJAX on that view

See #1376686: Error with Ajax enabled views in admin overlay for jQuery 1.7 and Views 3 or #1806894: An AJAX HTTP error occurred. for more information, and related issues.

Hope that helps. I recommend getting clean URLs to work. Not sure when non-clean URL sites will be fully supported by Views.

Tashko’s picture

Tashko CreditAttribution: Tashko commented

Thank you and it was an easy matter to switch Clean URLs on.

Since Clean URLs 'off' seems to be the default state for Drupal and since Quiz pagination does not work in the default state, it might be worth while logging that as a Known Issue so the next person to install quiz doesn't have the same problems.

Perhaps Clean URLs could be logged as a module dependency like many others are? Not sure if that is possible or not.

djdevin’s picture

djdevin
Location Philadelphia
CreditAttribution: djdevin as a volunteer commented

Clean URLs are on by default unless the installer thinks your server cannot support it: https://www.drupal.org/docs/7/configuring-clean-urls/enable-clean-urls

But Quiz isn't dependent on clean URLs being on, really no module should be.

Unfortunately you ran into the perfect storm of quirks and webserver configurations that causes any AJAX view to fail which is not specific to this module.

The first place to start when researching an issue is the Drupal issue queues - so if someone were to have an issue and search they'd find it here.

You may want to continue this in the related issue above since that seems to be the continuation of #1359798: Clean urls off break all Ajax views