by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 29 14:37

    jlambe on 2.0.7

    Update framework version to 2.0… (compare)

  • May 29 14:31

    jlambe on 2.0

    Fix syntax on phpunit test. (compare)

  • May 29 14:19

    jlambe on 2.0

    Fix Mix helper path. Add manife… Update Mix helper test paths. (compare)

  • May 20 10:01
    edwinsiebel commented #779
  • May 20 10:00
    edwinsiebel commented #779
  • May 19 18:59
    jlambe commented #779
  • May 19 18:28
    edwinsiebel commented #779
  • May 19 12:16
    jlambe closed #779
  • May 19 12:16
    jlambe commented #779
  • May 19 10:19
    edwinsiebel opened #779
  • May 18 05:20
    tavo1987 commented #774
  • May 17 11:01

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 17 11:01

    jlambe on 2.0

    Bump acorn from 6.4.0 to 6.4.1 … Merge pull request #776 from th… (compare)

  • May 17 11:01
    jlambe closed #776
  • May 15 16:50
    jlambe commented #760
  • May 15 16:44
    jlambe labeled #775
  • May 15 16:44
    jlambe commented #775
  • May 15 16:42
    jlambe commented #777
  • May 15 16:37
    jlambe commented #778
  • May 15 16:35
    jlambe unlabeled #778
swaraasolutions
@swaraasolutions
@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
swaraasolutions
@swaraasolutions
@jlambe have added my first pull so let me know if there are any issues
Julien Lambé
@jlambe
@swaraasolutions I’ll checked it. Thanks!
Nicholas Tsim
@ntsim

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 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?

Julien Lambé
@jlambe
Hi @ntsim, personally I keep my views inside the theme. The idea is to still be able to swap all application output by simply changing the theme. I use root application views for « shared » views or for anything that goes inside the WordPress administration.
Nicholas Tsim
@ntsim
Awesome thanks for the input @jlambe. I think I'll go with this approach so I'm not going too far off the Themosis way of doing things :thumbsup:
JasperV
@Mantik_gitlab
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/
swaraasolutions
@swaraasolutions
@jlambe excellent work with 2.0 just wanted to check when can we expect the infinite fields back in 2.0?
Julien Lambé
@jlambe
@Mantik_gitlab This is super cool! It would be cool to point to it somehow on the current documentation website.
@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 :(
JasperV
@Mantik_gitlab
@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.
But it'll be available on my site for a long time :)
I have a daily cronjob setup, so it automatically updates
mclaurent
@mclaurent
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?
mclaurent
@mclaurent
@mclaurent So I have worked out that this is set in app/config/session however I don't know WHY this would be needed? Is anybody able to shed light on the purpose of this and whether it is safe to remove?
Julien Lambé
@jlambe
@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.
jyme
@jyme
Hi everybody i have a question about Themosis v2.0 :). I would like to know if is possible to display Field in a metabox depending result from other field?
vasikgreif
@vasikgreif
@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?
mclaurent
@mclaurent
@jlambe Thank you - How do I go about removing it? I tried removing the config/session.php but that just caused an error, I think it's linked to the Symfony Request package.. Is there a setting I can set in the session.php to just disable that cookie?
Luke Abell
@LukeAbell
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
mclaurent
@mclaurent
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')
Maxime Freschard
@ligne13
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 !
mclaurent
@mclaurent
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 :)
Maxime Freschard
@ligne13
@mclaurent thanks for your feedback !
Raphael Pajak
@rafflex
Hi @jlambe what is you deployment workflow?
Rahajason
@lalainarahajason
Hi, i'm new to themosis, i have one question : how to check witch version i have ?
Marc Wieland
@marcwieland95
Do we have some guidlines how to use Gutenberg Blocks the best within the framework?
romainh
@romainhe
Hi! Can we ask support questions here? ^^