Add-on same thing as a package same thing as a block??
Permalink
I downloaded an add-on today and noticed that it was placed in the package directory (i.e. /concrete/packages/).
Then when I went to add it to a page it of course showed up as a block that I could add like any other block found in the /concrete/blocks/ directory.
This is confusing and I am wondering...
Add-on's seem to be packages. Are all add-on's packages? Do they all end up in /concrete/packages/ when they are downloaded and installed?
Is a package a block and a block a package? If not, how can I add it as a block?
Can I modify such packages/blocks by copying them to one of my custom directories (either /packages/ or /blocks/) and making changes to them there? If so which custom directory do I use? /packages/ or /blocks/?
Any insight anyone cares to share with me would be appreciated.
I just don't want to lead others wrong when I am trying to explain these terms in the future.
Thanks.
Carlos
Then when I went to add it to a page it of course showed up as a block that I could add like any other block found in the /concrete/blocks/ directory.
This is confusing and I am wondering...
Add-on's seem to be packages. Are all add-on's packages? Do they all end up in /concrete/packages/ when they are downloaded and installed?
Is a package a block and a block a package? If not, how can I add it as a block?
Can I modify such packages/blocks by copying them to one of my custom directories (either /packages/ or /blocks/) and making changes to them there? If so which custom directory do I use? /packages/ or /blocks/?
Any insight anyone cares to share with me would be appreciated.
I just don't want to lead others wrong when I am trying to explain these terms in the future.
Thanks.
Carlos
Excellent answer Mnkras. Just what I was hoping to see.
Thanks!
Carlos
PS. Oh...yes, I was mistaken about the download directory. You are of course correct.
Thanks!
Carlos
PS. Oh...yes, I was mistaken about the download directory. You are of course correct.
Mnkras you said...
"if your package for example has a block called "testing" in /packages/<pkgname>/blocks/ you can copy it to /blocks/ and edit it."
I copied the block inside the markdown package found in /packages/markdown/blocks/markdown/ to /blocks/markdown/ and edited the file edit.php and put some custom text in there.
Then I added the markdown block to a page and edited it within the admin interface and the custom text I put in did not appear.
Instead the C5 still pulled in the block found inside /packages/markdown/.
Is this just the case with markdown in particular that I can't seem to edit it without editing the version of it in the /packages/ directory?
Carlos
"if your package for example has a block called "testing" in /packages/<pkgname>/blocks/ you can copy it to /blocks/ and edit it."
I copied the block inside the markdown package found in /packages/markdown/blocks/markdown/ to /blocks/markdown/ and edited the file edit.php and put some custom text in there.
Then I added the markdown block to a page and edited it within the admin interface and the custom text I put in did not appear.
Instead the C5 still pulled in the block found inside /packages/markdown/.
Is this just the case with markdown in particular that I can't seem to edit it without editing the version of it in the /packages/ directory?
Carlos
Oops. Never mind. I can indeed edit the markdown block as expected and described.
I mistakenly thought what appeared on the screen when I indicated that I wanted to add it through the admin interface was the actual block I would be adding.
Apparently that was just what the block looks like. Until I pressed the
Add button it was not actually added but when I did my custom block changes appeared.
Thanks.
Carlos
I mistakenly thought what appeared on the screen when I indicated that I wanted to add it through the admin interface was the actual block I would be adding.
Apparently that was just what the block looks like. Until I pressed the
Add button it was not actually added but when I did my custom block changes appeared.
Thanks.
Carlos
Packages can contain themes, blocks, jobs, singlepages, and a number of other things.
concrete5 does not download the packages to /concrete/packages/ it downloads them to /packages/
if your package for example has a block called "testing" in /packages/<pkgname>/blocks/
you can copy it to /blocks/ and edit it.
Blocks are not packages.
Mike