Action::add method because it’s not handled by the service container, it is handled by call_user_func functions which cannot resolve dependencies. I’ve tried to find a way to make use of the service container for hook classes but without luck.
@jlambe When I call something like that:
$controller = new BlockController();
$controller->map($block, $content, $is_preview);I should be able to resolve models inside the controller, right? public function map(Post $post, $post_new) {
This is not the case. I get an error: Argument 1 passed to Theme\Controllers\BlockController::map() must be an instance of Theme\Models\Post, array given
map method signature is expecting as the first argument a Post model, your $block variable must be an instance of such model. The controller will not try to convert it if this is something you were expected.
- addLocation function under Finder.php the path is being defined however for windows the path starts with /D: due to this the assets are always not found if we remove the additional / in front of the path it works great
@swaraasolutions Thanks for reporting this issue. Can you post it under the framework repository or perhaps could you make a pull request? https://github.com/themosis/framework/issues Thanks
i will generate a pull request first thing monday morning IST
Hi @jlambe , loving the work on v2! I'm glad that someone is trying to make Wordpress bearable! :smile:
Just wondering what your feelings about where views/assets should go in the project structure. I'm getting the impression that these should generally be going in the project's theme directory, but for my use-case (a single Wordpress app), I can't really think of a compelling reason to do this.
My initial thoughts would be to actually hoist everything to root-level views/assets directories as it seems like it would make working on my project easier, particularly because:
- Not having to traverse down to the project theme to build assets
- More Laravel-y project structure
- Would make use of the root-level
viewsdirectory (would just be empty otherwise?)
On the other-hand, I'm quite new to Themosis, so I'm not sure if there are potential downsides to this kind of approach?
https://docs.jasperv.dev/themosis/2.0/
It's really easy to setup, so you could set it up yourself and host it on themosis.com. If you want the config I use just hit me up with a DM.
I have a daily cronjob setup, so it automatically updates
Has anybody had any issues with cookies being set automatically with the 2.x Themosis? I am seeing a "themosis_session" being set after setting up 2.0, but I have no idea where it is coming from or what it is being used for. It's causing me issues with page caching, and ideally would like to remove it as I don't believe it is being used anywhere?
echo app('Twig_Environment')->render('partials/global/activate/activate-header.twig')
- is it possible/recommended to use ACF with Themosis ? (to have Repeater or Flexible fields)
- i18n: is there an API for localization inside the Framework ? or should I still use the WPML plugin ?
- when creating a CPT with the PostType class, the post_content metabox/field is not present. Is this normal ? Should I add it manually by adding a custom metabox with a field named post_content ?
Thanks !
I am using ACF with Themosis and works really well. We're also using the flexible content fields, I think there's a guide on the ACF website on how to write that
i18n - we're also using WPML for this since the ACF-WPML integration works so well
Post types - sorry, I don't know the answer to this :)
Hello, i tried to upgrade the framework for a customer from 1.3 to 2.0 but when i go to the homepage it keeps telling we:
The theme is only compatible with the Themosis framework. Please install the Themosis framework.
I followed the documentation, but i kinda stuck in here. Can someone please help me? Cheers Rob
