Okay
  Public Ticket #3070566
CLI command to deactivate and create a theme is not working.
Closed

Comments

  • Adil started the conversation

    The following command is not working. 

    php artisan cms:theme:create demo
    

    I am looking to delete the current theme and create my own for this template. Please identify if I'm missing any important details.

    Attached files:  error-command-is-not-defined.jpeg

  • Adil replied

    Waiting for your response.

  •  238
    The replied

    Hi, sorry my documents are out of date. This section is not unavailable for now.

    So this command 

    php artisan cms:theme:create demo

    is not exist

  • Adil replied

    Please update the documents. The offline documentation is not working at all. I see that the issue was reported in 2021 but the links are still broken.

    Now, how can I create my own theme? I want to integrate my theme designed with React. 

  •  238
    The replied

    You can rename the current theme

    php artisan cms:theme:rename


  • Adil replied

    Is renaming the same thing as creating? I'm expecting a more helpful answer that actually helps me understand the steps for redesigning the whole theme? Not the backend, not the core. Just the theme!

  • Adil replied

    Waiting for your kind response.

  • Adil replied

    I'm still waiting for your response.

    I'm looking to integrate my React design. Please guide. 

  •  238
    The replied

    Maybe rename can cause some issues. You can update directly n our theme

  • Adil replied

    Which files are responsible for that? I'm missing the entry point to hook my theme with this.

  •  238
    The replied

    Hi,

    You can customize our theme in platform/themes/resido.

    You can create a new theme, e.g: platform/themes/demo or just rename the existing theme using command php artisan cms:theme:rename resido demo (then it will rename theme Resido to Demo).

    You can put your css/js/images in platform/themes/[theme-name]/public then run command php artisan cms:theme:assets:publish to bring those assets to /public/themes/[theme-name] (make it accessible).

  • Adil replied

    Ok, the assets are now published and can be seen in public folder. After following these steps, I've activated the theme from the dashboard. But getting error 404 on browser. Screenshot is attached for reference.

    What further steps do I have to follow now? Please guide.

    Attached files:  error404.jpeg

  • Adil replied

    Also, I have removed the default 'resido' theme using CLI command. Now it's giving error 500 on browser. See attachment for reference.

    Attached files:  error500.jpeg

  •  238
    The replied

    Resido as default theme, so you shouldn't remove this theme.

    You can enable debug in .env and see the error message. change  

    APP_DEBUG=false

    to 

    APP_DEBUG=true


  • Adil replied

    After a little progress, the controller seems to be missing. The error says BindingResolutionException | Target class does not exist. Looking for further guidance on this. Screenshot is attached for reference.

    Attached files:  error-ControllerNotFound.jpeg

  •  238
    The replied

    HI Adil,

    Please , You check file theme.json in the folder theme.

    platform/themes/resido/theme.json ( same same)

    9907038482.png


  • Adil replied

    I have updated the theme.json file data, republished the assets and activated the theme again. But I'm still getting the same error. What else am I missing here?

  •  238
    The replied

    Please make sure the folder path is exist. As saw the error message say that platform/Theme/xxx

    Our source code dont have Theme folder, it should is themes

  • Adil replied

    I have attached a screenshot with highlighted sections. Please review and help me understand the issue. 

    Attached files:  IMG-20220628-WA0015.jpg

  • Adil replied

    Waiting for your response

  •  238
    The replied

    Did you copy our theme and rename it manually or using the command ?

    And it should is Theme\Businesspost\Http, not Theme\businesspost\Http

    Run composer dumpautoload to update your changes

  • Adil replied

    I renamed the theme using CLI command. The previous error is now gone. However, the view is not getting rendered. I've followed the steps from the documentation and the default Resido template. Attaching screenshots for reference.

    Attached files:  IDE-error.jpeg
      IDE-view-not-found.jpeg
      Output-view-not-found.jpeg
      Output.jpeg

  •  238
    The replied

    themes/your-theme/views/index.blade.php

    This field should exist

  • Adil replied

    The field already exists. Attaching screenshot for reference.

    What else might be missing?

    Attached files:  view-not-found-IDE.jpeg

  •  238
    The replied

    I dont have ideal about that when I'm not sure you have deleted some files.

    Let give me the your theme, I will check

  •   Adil replied privately
  • Adil replied

    Waiting or your response on this, let me know if it would take longer. Thanks.

  •  238
    The replied

    I think you can remove 

    $theme = Theme::uses('Businesspost')->layout('mobile');
  • Adil replied

    No, It didn't work. Please see the attached screenshots

    Attached files:  IDE.jpeg
      error-output.jpeg

  •  238
    The replied

    Are you developer? When you want to customize something that mean you need to have a knowledge about coding.

    The error message show mix undefined. Please remove it


    Keep in mind that as support policy, we won't support customization, we just support our existing code https://codecanyon.net/page/item_support_policy


  • Adil replied

    Yes, I'm a developer myself. I have knowledge about coding but since your documentation is outdated so I need you to guide me through each step on how to make it work according to my requirements. It clearly does not 'works as described'.

    In your last reply, you are saying contradictory statements. Please be clear on this whether I can customize it or not? I have to use Laravel Mix. Does your template support it?

  •  238
    The replied

    + First of all we apologize for the document as it confused for you when document was out of date

    + We dont use Laravel mix in our site, you can refer this to know more https://laravel.com/docs/8.x/mix

    + We only support for any issues caused from our side. If your customize and make any mistakes, we will not support this