Forums | Mahara Community

Open Discussion /
bug report


anonymous profile picture
Account deleted
Posts: 6

18 November 2012, 4:52

Performing upgrades...

Component or pluginFrom versionTo versionInformation
artefact.blog 1.1.0 1.1.0 :) Successfully upgraded to version 1.1.0 (2011091400)
artefact.file 1.2.0 1.2.1 :( DirectoryIterator::__construct(/home/justican/.cpanel/quickinstall/mahara-/uploaddir/artefact/file/originals/) [directoryiterator.--construct]: failed to open dir: No such file or directory
Call stack (most recent first):
  • DirectoryIterator->__construct("/home/justican/.cpanel/quickinstall/mahara-/upload...") at/home/justican/public_html/mug/artefact/file/db/upgrade.php:405
  •   xmldb_artefact_file_upgrade("2010012702") at/home/justican/public_html/mug/lib/upgrade.php:374
  •   upgrade_plugin(object(stdClass)) at/home/justican/public_html/mug/admin/upgrade.json.php:94
notification.internal 1.0.1 1.0.3  
blocktype.externalfeed 1.0.2 1.0.3  
blocktype.file/gallery 1.0.0 2.0  
interaction.forum 1.2.1 1.2.1  
anonymous profile picture
Account deleted
Posts: 197

19 November 2012, 10:53

Hi Brooklets,

You can work around this by making the folder /home/justican/.cpanel/quickinstall/mahara-/uploaddir/artefact/file/originals/

A fix will come out eventually, but that should get you upgraded now.

Thanks,
Melissa

anonymous profile picture
Account deleted
Posts: 5

05 June 2013, 20:17

Hi we are getting a similar issue

DirectoryIterator::__construct(/var/maharadata/artefact/file/originals/.htaccess): failed to open dir: Not a directory

Call stack (most recent first):
  • DirectoryIterator->__construct("/var/maharadata/artefact/file/originals/.htaccess") at /var/www/htdocs/artefact/file/db/upgrade.php:416
  • xmldb_artefact_file_upgrade("2010012703") at /var/www/htdocs/lib/upgrade.php:374
  • upgrade_plugin(object(stdClass)) at /var/www/htdocs/admin/upgrade.json.php:94

This is a updating from 1.4.1 to 1.7.1... any advice would be appreciated!

Regards Daran

 

anonymous profile picture
Account deleted
Posts: 5

05 June 2013, 20:36

Solved, just removed the .htaccess file.... This was a clone of our production server, not sure if that was involved in the issue?

4 results