Hi,

ralouphie/mimey is not our package so we can’t update it.

Some packages don’t work on PHP 8 so you shouldn’t use PHP 8 in this time.

Thanks!

Also, Is it possible to give a list of updates, so that one can sync affected files incase customization has been done?

Thanks

Hi,

You should do a full upgrade. Too many files are changed https://prnt.sc/y9xqdc, https://prnt.sc/y9xtyo, and https://prnt.sc/y9xvgs

Thank you for the screenshots. Quite helpful.

Whats the best way to override the default member auth routes and view files?

Hi,

There’s no way. You have to customize it in platform/plugins/member.

Thanks.

Would you mind to explain a scope is, and what it does and how to manage/customize it? Tried to look through the documentation bu there is not concise well detailed explanation.

Also, is there a way to get the current activated theme?

Hi,

You can use

\Theme::getThemeName()

Thank you!

Would you kindly explain what a scope of a theme is, and it’s uses and effects? I haven’t seen any detailed explanation in the docs.

thanks

Hi,

Please check our docs here: https://docs.botble.com/cms/5.13/theme

Themes are located in /platform/themes folder.

Also, I would like to switch to database sessions. would that be feasible?

php artisan cms:plugin:create support

Command "cms:plugin:create" is not defined.

Did you mean one of these?                   
    cms:backup:create                        
    cms:plugin:activate                      
    cms:plugin:activate:all                  
    cms:plugin:assets:publish                
    cms:plugin:deactivate                    
    cms:plugin:remove                        
    cms:user:create

create plugin is not working

Hi,

Dev tools are removed in the download package, you need to delete folder /vendor and run command composer install to reinstall it, then you can use dev commands.

Screenshot from our docs: https://prnt.sc/z5h1g5

there is a potential bug here:

after creating a plugin, and creating seed data and seeding. seed data won’t load but only the data that you create with the form will load up. but when you query directly, all data shows up. is there a way to fix this issue?

Hi,

Which’s data not showing? I think maybe it has cache issue on your server.

We are using that seeder too and it’s working fine for us.

It has data in database so it should show on your site as normal.

Thank you! i agree with you it must be cache issue.

When i initialize a fresh installation with the data that you have provided, it works just fine. but now when i create a new plugin, then create a seeder, seeded data doesn’t load in datatables. but plugins like contact and blog show seeded data just fine.

so i think there’s a potential bug when you create a new plugin, seed data doesn’t load in the datatables. could there be a fix or can you guide on where i can get this issue fixed?

I’m not sure. I think it has wrong with your seeder.

Please create a ticket on our ticket system https://botble.ticksy.com and provide some screenshots about your code.

Our dev team will support you tomorrow (it’s a bit late in our time now).

Thanks!

You can try from your end. create a new plugin, then create some seed data, then try seeding, and see. only data that you create through he form will be visible in the datatables

thanks. done!

Hi,

Our CMS is based on Laravel framework 7.x so it supports Redis.

You just need to config to use it https://laravel.com/docs/7.x/redis

Are you using Ripple theme? Please give me your site to check it. Maybe you query the database too much.

Hi,

1. Drag and drop fields inside repeater field is not implemented, we will check and do it.

We will add date, time, and color field soon.

To display custom fields on all pages, check this screenshot https://prnt.sc/wngvgv

We will validate data for the select field.

For the name “Custom fields”, we don’t want to translate it at this time.

If you can, please create a ticket on our support center https://botble.ticksy.com, it’s easier to manage ticket and notify you when it’s fixed.

We have many comments on Codecanyon so it’s not easy to find it again.

Thanks!

Thank you for your response. About the change of “Custom fields” to “Custom Fields”, it is only changing f to F. It’s not a translation thing.

Thank you for your comment about drag and drop and work on the extra field type additions.

In your screenshot about the condition for assigning to “ALL” pages, you selected “model”. Is “model” your equivalent to WordPress’ “post type”?

Hi,

1. For “Custom fields” title, you can update it on your website in resources/lang/vendor/plugins/custom-field/en/base.php line 5. We will update it in the next version.

2. Model same as type.

Thanks!

Is it possible in the next release to allow for field conditions in custom fields as well? Having conditions would be tremendously helpful just like ACF does it.

I just changed the order value to 5, and still nothing.

I notice that when I have a group assigned to a page, the following view is loaded according to the Laravel developer tools. But nothing shows.

plugins/custom-field::_script-templates.render-custom-fields (\platform\plugins\custom-field\resources\views\_script-templates\render-custom-fields.blade.php)

If the custom field group is not assigned to a page, the above view is not loaded. So something is being loaded, but the fields do not show up.

I just created another group for all pages not “Homepage”. That group shows up on all pages. So perhaps there is something wrong with the condition for “Page is equal to X”.

Hi,

I have just tested on our demo site and it’s working fine.

Custom fields setup: https://prnt.sc/wklx00

In the contact page: https://prnt.sc/wklxj9

You can see it here: https://cms.botble.com/admin/custom-fields/edit/1

And it’s showing here: https://cms.botble.com/admin/pages/edit/1

What’s your CMS version?

How do I get the CMS version?

I found it – 5.11

I found package.json in the root of the laravel installation. Perhaps that is what is used for controlling webkit for theme development?

When running npm run development, I always get an error. In the root webpack.mix.js, I have:

let mix = require(‘laravel-mix’); let glob = require(‘glob’);

mix.options({ processCssUrls: false, clearConsole: true, terser: { extractComments: false, } });

// Run all webpack.mix.js in app //glob.sync(’./platform///webpack.mix.js’).forEach(item => require(item));

// Run only for a package // require(’./platform/packages/[package]/webpack.mix.js’);

// Run only for a plugin // require(’./platform/plugins/[plugin]/webpack.mix.js’);

// Run only for themes glob.sync(’./platform/themes/MYTHEME/webpack.mix.js’).forEach(item => require(item));

I always get the error:

npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js—progress—hide-modules—config=node_modules/laravel-mix/setup /webpack.config.js` npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the @ development script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\xxxxxx\AppData\Roaming\npm-cache\_logs\2020-12-26T18_53_17_173Z-debug.log

Hi,

Change [package] by the name of package you want to compile js/css. Do the same for [plugin].

I did this already but still not working. I’ve opened a support ticket with you on this. Please help at your earliest convenience. Thanks

You should revert our webpack.mix.js back as original.

We are using Laravel Mix https://laravel.com/docs/8.x/mix, you shouldn’t modify our config if you are not sure about it.

I’ve not modified the config at all. Please do not assume I’m modifying it. It will not work whether using ** or adding the name of my theme. Please look at the error message I provided you in the support ticket. I need help with this issue so I can get past this.

I’ve even updated node and npm on my system, and have tried modifying PostCSS as other’s have talked about in other threads.

Sadly, you didn’t care to help me, and instead assumed that I was messing with things. So I gave you a 1 star review.

Solution for others having the same issue:

1.

npm uninstall tailwindcss postcss autoprefixer

npm install tailwindcss@npm:@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9

npm run dev

Hi,

It’s a new issue with PostCSS. We actually don’t know about that issue until today.

Refs:

- https://stackoverflow.com/questions/64057023/error-postcss-plugin-autoprefixer-requires-postcss-8-update-postcss-or-downgra

- https://github.com/postcss/postcss-import/issues/435

- https://github.com/tailwindlabs/tailwindcss/issues/2799

It’s not easy for us. Laravel Mix has many issues on local environments https://github.com/JeffreyWay/laravel-mix/issues and we can’t know all issues to fix it, that why I have asked you to give us more info.

Thanks for your solution, we will update package.json with that changes.

We are on holiday (Christmas and New year) so sometimes it takes time to respond to you.

Thanks for your patience!

One strange thing here, we don’t define tailwindcss in package.json so you don’t need to uninstall it.

I think that issue happen when you install tailwindcss package.

Our package.json

{
    "private": true,
    "scripts": {
        "dev": "npm run development",
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "npm run development -- --watch",
        "watch-poll": "npm run watch -- --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js",
        "prod": "npm run production",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js" 
    },
    "devDependencies": {
        "axios": "^0.19.2",
        "bootstrap": "^4.5.3",
        "cross-env": "^7.0.3",
        "epic-spinners": "^1.1.0",
        "jquery": "^3.5.1",
        "jquery-nice-select": "^1.1.0",
        "laravel-mix": "^5.0.9",
        "lodash": "^4.17.20",
        "popper.js": "^1.16.1",
        "resolve-url-loader": "^3.1.2",
        "sass": "^1.30.0",
        "sass-loader": "^8.0.0",
        "tachyons": "^4.12.0",
        "vue": "^2.6.12" 
    },
    "dependencies": {
        "@fullhuman/postcss-purgecss": "^3.1.3",
        "bootstrap-vue": "^2.21.1",
        "cropper": "^0.7.9",
        "moment": "^2.29.1",
        "sanitize-html": "^1.27.5",
        "toastr": "^2.1.4",
        "vue-template-compiler": "^2.6.12" 
    }
}

tailwindcss uninstalled, and now get the following error regarding postcss-loader:

ERROR in multi ./platform/themes/r1l/assets/js/r1interactive.js ./platform/themes/MYTHEME/assets/scss/style.scss Module not found: Error: Can’t resolve ‘postcss-loader’ in ‘C:\xampp\htdocs\SITE’ @ multi ./platform/themes/MYTHEME/assets/js/MYJSFILE.js ./platform/themes/MYT HEME/assets/scss/style.scss /themes/r1l/js/MYJSFILE¹

Hi,

Can you show me file platform/themes/r1l/webpack.mix.js?

This file is not existed ”./platform/themes/MYTHEME/assets/js/MYJSFILE.js” so it throws error.

Same for file ./platform/themes/MYTHEME/assets/scss/style.scss

I’m renaming that file so I don’t have actual file names here. I put all of this in the ticket at https://botble.ticksy.com/

Hi,

For postcss-loader, maybe you need to run those commands:

npm uninstall postcss-loader --save-dev
npm install postcss-loader@~3.0.0 --save-dev

It’s an issue with PostCSS, they have released version 8 and it breaks all projects using PostCSS.

I have replied on https://botble.ticksy.com/ticket/2642205, please check the latest reply.

Hi,

I think it’s an issue with memory limit.

Please enable “Chunk size upload” in Admin -> Settings -> Media and try again.

Screenshot: https://prnt.sc/w0x4i9

I try change it

but still same issue, plaese check screenshot: https://prnt.sc/w16c6j