Re install the standard Survey block
Permalink
Guys,
I was having problems with this so uninstalled it intending to reinstall.
When I now go to Addons and try and find it to re install there is no sign of it. Does anyone know where I can re find the survey block!?
Ian
I was having problems with this so uninstalled it intending to reinstall.
When I now go to Addons and try and find it to re install there is no sign of it. Does anyone know where I can re find the survey block!?
Ian
Thanks Greg, all done.
Btw why do we put it in the root/blocks folder rather than root/concrete/blocks?
Ian
Btw why do we put it in the root/blocks folder rather than root/concrete/blocks?
Ian
I am not exactly sure why that is. If it is very important for you to know, I will certainly find out why from someone more senior. The reason it doesn't just show up in your "add functionality" area is because c5 does not look in concrete/ for new stuff. My understanding of it is that c5 does not look in the /concrete/ folder for new stuff mainly because looking for something new in there is contrary to c5's architecture, and possibly because it has so much existing stuff to parse. And in the general case there is no reason to track "old stuff" because most things exist as installed or ready to install.
An example of a benefit of doing it this way from an architect's standpoint would be to consider a scenario where you inherited a c5 site created by some really gung-ho individual. Hopefully even if they only had a slight understanding of that architecture, you would be able to find all their changes and new blocks without any problems.
An example of a benefit of doing it this way from an architect's standpoint would be to consider a scenario where you inherited a c5 site created by some really gung-ho individual. Hopefully even if they only had a slight understanding of that architecture, you would be able to find all their changes and new blocks without any problems.
because /concrete is the core, and anything above it are your overrides to that core.
You shouldn't be messing with the core at all if you ever want to upgrade.
Man we need in info-graphic explaining why/how overrides work.
You shouldn't be messing with the core at all if you ever want to upgrade.
Man we need in info-graphic explaining why/how overrides work.
Ian: the system is set up this way to solve a problem that exists in many other CMS's -- often times people want to make customizations to the core code, and they do so, but then when it's time to upgrade the system, the new upgrade completely overwrites the customizations they had. By copying the files out into a different directory and making the changes there, it means that when the system is upgraded it will *not* overwrite the customizations you made.
Guys, thanks to all three of you for your help. I never knew that about the root/concrete structure. No more fiddling about in there I guess. As frz said some notification of this to all wouldnt kill.
to reinstall a block that has been removed, you need to copy that block out of the [webroot]/concrete/blocks/ up into [webroot]/blocks/
So in your case you can do that by
over SSH, usually from your public_html or www or whatever your hosting company named the public facing section of your account. Or you can do that on FTP, a cPanel-type file manager, etc...*
Then you can go back to "Add Functionality" on your dashboard and you will see your missing block in the right-hand column. Once it's installed you can go ahead and actually remove the copy of the block in [web]/blocks/ That way if there is a change during an upgrade, your copied block won't override the existing one.
* If your site has a "concrete5.4.1.1" folder in updates, you will want to copy THAT block down into your webroot. That will be the most recent version of the block.