I want to replace the free BSB theme in aspnetboilerplate project (Angular + ASP.NET Core) with a custom theme. Are there any instructions of how to do it?
Or at least a clue of what needs to be updated on client side?
I've changed the bsb template in a lot times and what do is the next:
Put the new template elements in the Abp's angular project in the same place that it in the new template, for example if en src/app there is an "Example" folder I copy this to the Abp's template
Delete Bsb theme (if you have problem with tenant, user, or roles foler, erase it too) folder and find the places where Abp's project use, regular is in angular.json
Edit Package.json file and put all packages from new template without erase the packages from the abp's orignal Package.json file, angular will say you which files are repeated on the file, then you keep the most recent.
Do the same with Angular.josn file, be sure to load all files that load the new template.
Design again the base register from abp's template based on the new template, for example if your new template has a example login page, on the .ts you put the code of the orignal abp's template, like this you will have the new design with same abp's logic.
https://github.com/domisysdo/Colegio.Client
In this project I've putted Adminca Template on Abp's project you can download it and check it if it can help you.
Related
I am new to Laravel 4, and I come from a Zend Framework background. I'd like to create a folder app/forms and keep all my forms there. How can I refer to the form in the controller and within the view.blade files?
By default, the root of the view files folder is app/views so if you create a folder in views like app/views/forms then you may refer the form by it's name from a controller like:
$form = View::make('forms.formfile');
Here, formfile is the name of the file that contains the form and it could be formfile.blade.php and to refer/include the form file from a view you may use #include:
// In a blade view file
#include('forms.form1')
Assume that, form1 is a blade view inside the forms folder and saved as form1.blade.php, you may also use sub-folders inside the forms folder, for example in views/forms/user folder you may keep a view named index.blade.php and use it like:
// From a controller
$userForm = View::make('forms/user/index');
From a view file: (folders are separated by .)
#include('forms.user.index') // file: app/views/forms/user/index.blade.php
You can also nest views in the controller, check the manual for more.
From the standpoint of Laravel, HTML forms (and all presentation related things ) belongs to app/views/ folder. Exceptions are package specific views. For example some commands has their own stubs and views and they are usually stored inside package.
Laravel is very flexibile, and you can move things around and create new folders and namespaces. You just have to tell composer that you are changing Laravel default structure, and dumpautoload. That is if you only want to create new folder with internal reference. If you want something with more scope and visibility you'll have to bind that to container, so that will be visible inside whole application.
You are coming from the Zend world, so I can understand that you want to move some of Zend "flavour" to Laravel. Although is it possible, I would really recommend you to take some time and learn how Laravel works. There are some great ideas and design inside. Of course, Zend has its own quality, but hey - this is Laravel :)
Anybody know how to add custom fields, new fields to enter some values with joomla 2.5 articles in backend.
I want to add some values when i create an article and want to get these values in frontend.
Is there any way i can do this??
Any help will be appreciated.
Thanks in Advance
Tibin Mathew
I think Joomla team predicted that in some way:
Joomla step by step
you would have to
Modify the _content database table
_content is the suffix name of the table that contains all the articles. If you want to add new fields you have to modify this database table to reflect those new fields.
com_content files
com_content is the component in control of articles in both the frontend and backend. It can be found under the components folder under the main directory, and in the administrator/components folder under the main directory. The files in com_content control how the articles are displayed how the form is displayed how actions like save unpublish etc work. So these files will have to be edited to work with your new fields
xml files in the models/forms models/fields
There are XML files under these folders within the com_content folder that tell how the edit form of articles are supposed to be viewed, what type of fields are used, etc. These will have to be modified to reflect your new fields
then you have to do it all again
Each update has updates to the core files (com_content is a core component so all its files are core files). If you go about editing the files in com_content and then do an update these files are more then likely will be overwritten by the update basically losing your modifications. So you would have to redo the modifications.
It is better to make your own component
I'm new to joomla and have got a problem with a website.
I need to modify a view and I've been told it is in
http://www.example.com/index.php?option=com_user&view=register&Itemid=68
It has a registration form and i need to modify its field. I've access to FTP only. I need to know where are these files to modify the registration form. If one can describe the meaning of this url structure then it would be very helpful.
You will find the template files in /components/com_user/views/register/tmpl.
However, you should create an html/com_user folder in your template directory with a copy of those files and use a template override ("never" edit core files).
Here are a couple resources that will point you in the right direction:
http://docs.joomla.org/J2.5:Developing_a_MVC_Component/Introduction
http://docs.joomla.org/How_to_override_the_component_mvc_from_the_Joomla!_core
com_user means use the user component register view.
Itemid 68 refers to the id of the menu item it is linked from.
You don't want to directly modify any joomla files.
If you want to add a field to registration activate the user plugin or create your own user plugin along the same design but with the fields you want.
It is advisable not to modify the core files directly, they will get overridden whenever the Joomla is updated.
However what you are looking for is available at components\com_users\models\forms\registration.xml file. you can change the default fields of the registration form in this file.
If you would like to add additional fields to registration form, there is a better way:
http://docs.joomla.org/Creating_a_profile_plugin
I'm prepare a multistore on magento.
I have a three template, and I was change a few file from code/core and replace in code/local, but only one template take a changing code from code/local
a rest template should take file from code/core/
Now every template take files from code/local/
How can I'm set app to resolve a problem
thx for help
You should NOT overwrite core files in local. Better try to develop your own module which rewrites the core functionality. In this module you can integrate a configuration, so it's only used for one store view, and not for all.
I have a need to create my own DNN installation package that will include my custom modules and skins along with pages and sample data. Is there a way to do that?
You can setup the site how you want it (with the pages and sample data), and then Export a Portal Template from the Host -> Portals/Sites page.
Then, when you create a new site, add that template to the Portals/_default folder (alongside Default Website.template), and you can select that template when installing the site. Make sure that you also include the packages for your custom modules and skins in the corresponding folder (Module or Skin) in the Install folder.
In terms of sample data, only data in "portable" modules will be included in the template. This includes the HTML module. If you need sample data to come along with your custom modules, your business controller class will need to implement IPortable.