Bug #4229

Fatal errors when sfIsadPlugin is disabled

Added by David Juhasz about 10 years ago. Updated almost 9 years ago.

Status:VerifiedStart date:
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:

0%

Category:-
Target version:Release 1.4.0
Google Code Legacy ID:atom-2281 Tested version:
Sponsored:No Requires documentation:

Description

To reproduce this error:

1) Disable sfIsadPlugin at "Admin > Plugins"

2) Choose any template other than ISAD at "Admin > Settings > Default template > Archival description"

3) Go to any one of the following pages:

  • Duplicate description ([View archival description] > Duplicate)
  • Link digital object ([View archival description] > Link digital object)
  • Import digital object ([View archival description] > Import digital object)
  • Physical storage location report ([View archival description] > report > physical storage locations
  • Box list (Manage > physical storage > [storage location name] > reports > box list])
  • Term browse (Browse > subjects > [subject name])
  • Any autocomplete that contains archival description titles (ISAAR, ISDF, ACL, etc.)

Resulting error:

Something similar to:

Fatal error: Class 'sfIsadPlugin' not found in /home/david/public_html/qubit/apps/qubit/modules/informationobject/templates/multiFileUploadSuccess.php on line 5

Expected result:

No error

[g] Legacy categories: Information object


Related issues

Related to Access to Memory (AtoM) - Bug #4228: Fatal error editing digital object when sfIsadPlugin is d... Verified
Related to Access to Memory (AtoM) - Bug #4226: Fatal error for EAD Export when sfIsadPlugin is disabled Verified

History

#1 Updated by David Juhasz about 10 years ago

See /p/qubit-toolkit/issues/detail?id=2280, /p/qubit-toolkit/issues/detail?id=2278 & /p/qubit-toolkit/issues/detail?id=2277

#2 Updated by David Juhasz about 10 years ago

  • Subject set to Fatal errors when sfIsadPlugin is disabled

Fix typo in issue title.

#3 Updated by David Juhasz about 10 years ago

  • Target version changed from Release 1.2.1 to Release 1.3

[g] Labels added: Milestone-Release-1.3
[g] Labels removed: Milestone-Release-1.2.1

#4 Updated by David Juhasz almost 10 years ago

Reassign to new account.

[g] New owner: David Juhasz

#5 Updated by David Juhasz almost 10 years ago

  • Priority changed from High to Medium

[g] Labels added: Priority-Medium
[g] Labels removed: Priority-High

#6 Updated by Jesús García Crespo over 9 years ago

  • Assignee changed from David Juhasz to Jesús García Crespo
  • Target version set to Release 1.4.0
  • Sponsored set to No

#7 Updated by José Raddaoui Marín about 9 years ago

I don't get the error in any of those cases. May be already fixed?

#8 Updated by José Raddaoui Marín about 9 years ago

  • Status changed from New to QA/Review

#9 Updated by Dan Gillean almost 9 years ago

  • Status changed from QA/Review to Feedback

1) Disable the ISAD plugin
2) Go to Add > Functions: error
3) Enable ISAD plugin, and repeat action. ISDF template works.

I'm having issues with digital object linking in the dev branch (leads to server error)as well, but the result is the same whether or not the ISAD plugin is enabled or not. But due to this, I can't yet guarantee that the ISAD plugin won't affect Digital object linking. Will continue separate from this issue to determine cause of the image linking error, and will file a ticket if necessary, as it could be a regression. In the meantime, all other listed tasks in the issue ticket seem to be performing as expected.

#10 Updated by Dan Gillean almost 9 years ago

  • Description updated (diff)

#11 Updated by José Raddaoui Marín almost 9 years ago

  • Assignee changed from Jesús García Crespo to José Raddaoui Marín

I can't replicate those errors Dan, could you give me more information please?

#12 Updated by Dan Gillean almost 9 years ago

  • Status changed from Feedback to Verified

hmm, i just re-tested, and couldn't reproduce - worked fine on multiple browsers, including FF, which I tested with last time. Going to mark verified for now, as all behaviours seem to be working as expected now. Will file a new issue if anything else occurs.

Also available in: Atom PDF