short question regarding the needed extensions: the intl extension is already bundled with php, right?
This extension is bundled with PHP as of PHP version 5.3.0. Alternatively, the PECL version of this extension may be used with all PHP versions greater than 5.2.0 (5.2.4+ recommended).
On a Homestead environment it is enabled and normally most host providers compile it.
@JaspervanV_gitlab The custom fields interface is built only with javascript. When you define a custom field for a metabox, its UI is handled by a js component built with ReactJs. This is only available when working with metabox and custom fields. Custom fields for settings page or regular forms, are html only.
@marcwieland95 Basically controller dependencies are handled automatically wherever you use it. Auto-injection does not work if called from an
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
When calling a method directly, you have to pass expected objects. Personnaly I’ve never had to call a controller this way. So if your
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.
Do you already have any further ideas about using blocks inside Themosis?
@jlambe couple of issues i found when trying to integrate Themosis 2.0 on windows, linux worked like a charm
- 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
@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?
I'm hosting generated API docs of Themosis on my website. Some of y'all might find it useful. :)
https://docs.jasperv.dev/themosis/2.0/
https://docs.jasperv.dev/themosis/2.0/
@swaraasolutions No date defined yet. It might take a long time before it is merged back into core. I suggest you look at dedicated plugins like ACF for example if you need some sort of repeater field. Sorry :(
@jlambe thanks fam, it's generated with Sami; the same thing Laravel & Symfony use.
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.
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.
But it'll be available on my site for a long time :)
I have a daily cronjob setup, so it automatically updates
I have a daily cronjob setup, so it automatically updates
Hi
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?
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?
@mclaurent The themosis_session cookie is used in order to identify each user session. It's a random value generated by the session package in order to use session in your application for both anonymous users or authenticated ones. If you do not use session in your app, you can remove it.
@jlambe Hello , I can see there's support for handling the translations from the app directory (themosis/framework@5bf32e0), but I did not find an example on how to use that
am I missing something?
Hey guys! Long time Themosis user/lover. We're working on upgrading from v1.3 to v2. The only thing we're stuck on is getting routes to work in our theme. I'm registering them just like this but they aren't being honored https://github.com/themosis/theme/blob/master/resources/Providers/RouteServiceProvider.php#L32
Has anybody had any luck TWIGging the wp-activate pages? I.e. when a user account is activated we want that page to be in-brand rather than default WordPress? I think the only way would be using the tempate-parts folder which would then call a Twig template, like below, but that's less than ideal...
echo app('Twig_Environment')->render('partials/global/activate/activate-header.twig')
Hi! I have a few questions before migrating to Themosis:
- 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 !
Hey @ligne13 ,
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 :)
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 :)
