Main Menu
Contact
Popular Plugins
Sign In

NOTE for Windows systems, please replace all the / characters with \ when example commands are given below. If you are under *nix or MacOS X and you get a Permission denied error, you may need to run:

chmod a+x concrete/bin/concrete5

1. I get a message saying something like “Could not continue processing, probably this Block ...”. What should I do?

Scenario 1 – option 1

This is most likely due to the fact that “Block Cache” is enabled. You can disable it by running the command below:

concrete/bin/concrete5 c5:config set concrete.cache.blocks false

Afterwards, you should clear the cache too, which can be done with the following command:

concrete/bin/concrete5 c5:clear-cache

Make sure your /application/files directory is (still) writable too.

Scenario 1 – option 2

Alternatively, you can do the following too. This setting can be found in your concrete5 site under:

  • Dashboard
  • System & Settings
  • Optimization
  • Cache & Speed Settings

Set the value to “Off” instead of “On”. Afterwards, clear the cache too by going to the “Clear Cache” page and make sure the /application/files directory is writable.

Scenario 2

The other situation is that the Block Type is installed in a non-installed package. What you should do is install that specific package first and then try again. You can either use the command line by install a package:

concrete/bin/concrete5 c5:package-install your_package_handle_here

(don’t forget to change “your_package_handle_here” into your own handle)

Or navigate to Dashboard – Extend concrete5 instead and hit the “Install” button behind the package.

2. I’m getting a “Cache path is not writable.” message with all sorts of things afterwards. What’s all that?

This is because the cache path is not writable, which should be fixed by running the following command (in Linux/Mac OS):

sudo chmod -R 755 application/files/cache

3. When generating a Block Type, I get an error like "Writing files to new Block Type directory... copy(/public/application/blocks/my_block_handle/add.php): failed to open stream: No such file or directory"

This most likely means that you have no /public/application/blocks directory. Please create that first and set the proper read/write rights. If you meant to install this Block Type in an installed package, please use the package parameter or answer with "y" after you get the "Do you want to place this Block Type within an already installed Package" question.

4. After installing this Add-On in concrete5 version 5.7.x, I get an error message. It says: "An unexpected error occurred."

No worries now. This is to make this Add-On compatible for older versions of concrete5 too. The last version of 5.7.x was in 2016, so the consession is to have this error upon install only and let the rest remain as quick and clean as possible. You can navigate to any URL after installing this Add-On, without having errors.

Use, by you or one client, in a single end product. The total price includes the item price and a buyer fee.

  • Quality checked by Concrete5
  • Future updates
  • 30 Day Support
  • Concrete5 buyer fee: $32.70
Add to Concrete5 Cart

Use, by you or a client, in 5 single end products. The total price includes the item price and a buyer fee.

  • Quality checked by Concrete5
  • Future updates
  • 30 Day Support
  • Concrete5 buyer fee: $130.80
  • Save an extra: $109.00
Add to Concrete5 Cart

Use, by you or a client, in x/xx single end products.

Upon request, quote will be made and sent to you via email.

  • Quality checked by Concrete5
  • Future updates
  • 30 Day Support
  • Saves extra $$
Request Quote
Released 1 year ago
Updated 1 year ago
Requires concrete5 5.7.5.3
Current version 0.9.7
Skill level Bleeding Edge

Buyer Rating:

5 average based on 2 ratings More information

Got something to say? Need help?

View support forum