I have this error message after upgrade from 1.7 to 1.8.

and i really dont know how to fix that. Does anybody have the same question?

I really need some help.

CommentFileSizeAuthor
#5 screenshot-chen.vic_.tw 2015-06-24 18-23-07.png954.98 KBcobenash
螢幕快照 2015-06-24 下午5.34.21.png459.6 KBcobenash
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

cobenash’s picture

cobenash
Location Taipei
CreditAttribution: cobenash commented
Title: Fatal error: Maximum function nesting level of '100' reached, aborting! in /Library/WebServer/Documents/aphrodite/includes/database/query.inc on line 331 » Fatal error: Maximum function nesting level of '100' reached
Perignon’s picture

Perignon CreditAttribution: Perignon commented

Your image is cut off. Cannot see the ful stack trace.

No one else has reported an error like this upgrading to 1.8. What version did you have before? 1.8 is a very small change in the code base.

Also explain how you are using Storage API, be very specific.

cobenash’s picture

cobenash
Location Taipei
CreditAttribution: cobenash commented

@Perignon Thank you for your replied.

The Version I used was 7.x-1.7 and everything was great.

But when i use 7.x-1.8, i got the error message when i access the node edit page and the page with the block which Views Module created.

But it works fine at the node view page.

I have the several website use this module, and i got the same error message.

The Storage i used is Amazon S3.

Thank you.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

How have you implemented storage API? Is it a field attached to a node?

Also post the entire stack trace, the beginning of it (the bottom) is cut off in your attached image.

1.7 to 1.8 was a security update that changed the way file access was checked. I do not think it should be causing this error. We have only observed problems with 1.8 that were being caused by other modules looping on security checks against files.

cobenash’s picture

cobenash
Location Taipei
CreditAttribution: cobenash commented
FileSize
screenshot-chen.vic_.tw 2015-06-24 18-23-07.png954.98 KB

@Perignon
Yes, it's an image field attached to a node.
The New attachment is full screen capture image.
Thanks for helping.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Do you have access control turned on for that field instance in the Storage API container?

Perignon’s picture

Perignon CreditAttribution: Perignon commented

I see the problem. You are using CKEditor module aren't you?

cobenash’s picture

cobenash
Location Taipei
CreditAttribution: cobenash commented

Yes,I am using that.
But why the problem was happened not only at the node edit page?

cobenash’s picture

cobenash
Location Taipei
CreditAttribution: cobenash commented

@Perignon
Sorry, The problem is the same with https://www.drupal.org/node/2499135
I disable ckeditor and everything is fine,

Perignon’s picture

Perignon CreditAttribution: Perignon commented

So this is a duplicate issue. This has already been identified and the problem is being caused by CKEditor and not Storage API.

If you look in the stack trace of the errors you will see the function, ckeditor_file_download()

Perignon’s picture

Perignon CreditAttribution: Perignon commented
Related issues: +#2499135: Nested storage_core_bridge_storage_access Function Call
Perignon’s picture

Perignon CreditAttribution: Perignon commented
Parent issue: » #2499135: Nested storage_core_bridge_storage_access Function Call
Related issues: -#2499135: Nested storage_core_bridge_storage_access Function Call
Perignon’s picture

Perignon CreditAttribution: Perignon commented
Status: Active » Closed (duplicate)

There... Fixed the relationship. Marking this one as a duplicate.