jlambe on master
Update core events. (compare)
dependabot[bot] on npm_and_yarn
Bump axios from 0.18.1 to 0.21.… (compare)
jlambe on master
Refactor core bus classes and j… (compare)
jlambe on master
Update core Auth classes. (compare)
jlambe on master
Complete bootstrappers update. Update framework tests. (compare)
jlambe on master
Update interfaces on core appli… (compare)
jlambe on master
Add provider is loaded method t… (compare)
jlambe on master
Refactor exception handler. (compare)
jlambe on master
Update exception handler. (compare)
jlambe on master
update dependencies. Update dependencies. Start bootstrap refactoring. (compare)
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.
@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:
views
directory (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?
echo app('Twig_Environment')->render('partials/global/activate/activate-header.twig')
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
http://bookstore.dev/firstcategory/secondcategory/hello-world-post
, but not the archive
i have to reference http://bookstore.dev/secondcategory
currently but i need the parent/child category tree to be on the url
it's using the standard route currentlyRoute::match(['get', 'post'], 'archive', function ($post, \WP_Query $query) {