While configuring Gibbon, I deleted some fields in a form in the Admissions area. After I realised I needed them, I deleted the Admissions module and redownloaded from the GitHub. However, no description is shown for it in the modules page in my admin area and the admissions pages no longer work. I have installed and unzipped it, called the folder Admissions, and the only things inside it are what looks like the normal files.
Hi Sam, no worries, it sounds like you tried to solve it yourself and ran into some trouble. Data in Gibbon is stored in the database rather than the file system, so unfortunately even if you were successful, it wouldn’t have restored the deleted data.
When you deleted the Admissions module, did you only delete it from the file system, and not from the database? Core modules don’t have a delete button in System Admin > Manage Modules, so this would only be the case if you deleted it from the gibbonModule table. Otherwise, if the entry is still in gibbonModule, when you restore the files, it should connect up again. Can you check the file permissions of the files, and also ensure there are no nested folders, so that the folder is called Admissions and the contents are the same as other module folders. Hope this helps, let us know.
I deleted the entire module from the filesystem at /var/www/html/modules (rm -rf Admissions).
There are no nested folders, and I took the module directly from the GitHub repository. The contents look the same.
The module does appear as ‘installed’ in the System Admin > Manage Modules page, but it has no description unlike the others. No errors as far as I can see, and it never asked me to click install, it was just there. I didn’t touch the DB at all. My original goal was to restore the original student entry form because I deleted some fields… won’t do that again
Hi Sam, I’ve checked and it looks like the module doesn’t have a description, so that part is normal (I must have forgot to write one when adding it a few versions back). If you’ve replaced all the files as they were before, it should start just working again. The only other thing to check is file permissions, as the new files may not have server read/write permissions.
No worries. You can use the terminal to check the file permissions
ls -l path/to/your/file
This will list details about the file, including its permissions in a format like -rwxr-xr--. The letters show who can read, write, or execute the file. Hope that helps.