Provide details about the FieldRespositoryInterface instance attached to a form.

The repository() public method gives access to the list of fields added to a form.

please make that color to something readable, i think #fff is good.

pre.prettyprint {
...
color:#fff;
}

thanks

Write documentation about the loaded service container and informations about helper functions.

Provide the database guide documentation with information about loaded CapsuleManager.

A small typo in the Helpers page: https://github.com/themosis/documentation/blob/master/helpers.md#themosis_set_patharray-paths

themosis_set_path is supposed to be themosis_set_paths.

The subdomain installation has still a core issue regarding the management of the home_url database option value where it appends the cms URI.

Update the documentation to warn developers to manually update the database and fix the home_url value by removing the cms URI.

On installation guide, provide a note for the public directory.

Metabox API has a can() method that developers can use in order to limit the display of the metabox based on a role or capability.

// Metabox is viewed only by administrator...
Metabox::make('My Metabox for admin', 'page')->set()->can('administrator');

Add service providers documentation. How to best write service providers, how to register them.

Unhandled Exception

Message:

Argument 3 passed to Themosis\Asset\AssetFactory::add() must be of the type array, boolean given

I don't know for not display this message :

Your application do not handle the following plugin:

Inside the file, "Define your plugin theme support key. Once defined, make sure to add the key into your theme supports.config.php in order to remove this admin notice"

In the documentation is not really clear

Provide metabox mapping documentation...

The first parameter of a form is a DTO object. Form options need to be specified as a second argument on the factory make method.

Explain how to apply a custom prefix to fields attached to a custom taxonomy. A sample code can be found inside the following issue: themosis/framework#732

Only for documentation on framework 2.x

In assets documentation, version 1.3, remove the references to asset type options of 'js', 'css'. Not available 👎

Please help me. I can't make ajax form with Themosis framework. admin-ajax php 200 OK
What is the problem? I make anything wrong?
Thanx for you.

resources/admin/ajax.php
Ajax::run('send_contact_mail', 'both', function(){
echo 'assad';
die();
});

javascript file:
$.ajax({
url: themosis.ajaxurl,
type: 'POST',
dataType: 'json',
data: {
action: 'send_contact_mail',
}
})
.done(function(data) {
console.log(data);
});

Error 404 on "Introduction Guide" in the link at bottom of this page https://github.com/themosis/documentation
https://github.com/themosis/documentation/blob/master/%7B%7Burl%7D%7D

Hey, I have been using the Beta2 release of 2.0 and have been loving the changes so far.

However: it appears that the Taxonomy documentation has not been updated yet, while the interface for (at least) adding custom fields has clearly changed (with the removal of the addFields method and inclusion of the TaxField class).

It would be great to get clear documentation on this as the examples currently available are broken.

Thanks and keep up the great work!

I discovered that you can use a controller@action with ajax::listen, this is not documented. Note that you have to specify the full namespace - \App\Http\Controllers\Controller@Action

The web version of the site contains a navmenu with all documentation:

However, the mobile version of the site has no way to access these pages:

Add documentation regarding the new default theme.

Add information about GulpJS and WebPack configurations, BrowserSync, Bower, ...

Update routing documentation and add middlewares guide.

Regarding to the official Wordpress reference there are no fields called "email" or "url" which are mentioned in the Themosis User Docs.

The theme constant in the upgrade guide is wrong, people should replace with THEME_TEXTDOMAIN

Hi! I am a bit confused with the views share.

Where do i place this? in the routes? inside a route?

Can you give an example of how to use it in a route? and where to place it?

Hi Julien

First, thanks for your great work. Currently I'm developing my first project using Themosis, but when I read about use Homestead honestly I consider another way in roadmap, because "a machine inside machine" is very noise.

Please consider use Valet, for Mac developers. Valet is very simple and robust, recommended by Laravel, or another environments, for example: LocalWP (formerly Local by Flywheel) that's sound like available for Mac an PC users.

Now, if your framework supports Valet, do you have docs? In another issue, I'm read about php artisan serve, but the problem was ugliest url's, Valet solve it.

You can consider another documentation that not uses Homestead, too.

EDIT: Currently I'm running on Mac without Homestead using brew for install PHP/MySQL/nginx, and DBngin to manage SQL environments and Tableplus to manage databases.

Excuse my english and please use Valet :)

Hey Themosis Team,
Don't know where I have to post this, but i can't access to the "Plugin" documentation (link) the following message is displayed

Error establishing a database connection

Same message for the pages "wp-cli", "Multisite" and "Theme"

Hello,

The path for Facades\Twig in example from Extending Twig is incorrect;

Incorrect (Facade)

use Themosis\Support\Facade\Twig;

Correct (Facades)

use Themosis\Support\Facades\Twig;

I hope to be helping

I see you've added alot of new stuff in the dev-master especially the Helper class has been growed significantly. If you would like some help with documenting stuff Im willing to help you. If you are looking for some help, it would be easier for others if you could setup some list with "stuff to document'.

Great work on this, very awesome.

How would you guys suggest working with Custom Post Types that require multiple custom fields? Creating a proper Model for it would make the most sense, but this doesn't seem to support custom fields.

I was considering going with the "traditional" Pods plugin and see if the Model can still read from these, but maybe there's better practices in place already.

Thanks!

The docs explain how to pass data along with an include:

@include('header', ['title' => 'Documentation'])

...but, they don't explain how to consume that data in the included view.

header.scout.php

{{ title }} //Use of undefined constant title - assumed 'title'
{{ $title }} //Undefined variable: title

In order to help users contribute to the documentation, add an "Edit" link, on every pages, that redirects to the appropriate GitHub branch and file.

I can't load the View file from inside the controller method, I have tried this 2 solution and none of them works (I always get a message saying that the view is not found) :

1. return view('/newsLetter.twig');
2. return view(themosis_path('plugin.com.plugin.newsletter.resources').'views/newsLetter.twig');

note : the plugin works correctly if I echo the message directly from inside my controller and themosis_path('plugin.com.plugin.newsletter.resources') return a correct path to the plugin resources folder.

Hello,

I want to create a plugin with many page in the backend of wordpress. i want to reproduce a MVC structure and use twig view.

It's possible or not ?

Thanks

Hi @jlambe I'm ready to translate the documentation into my native language (pt-br), how do you think we could proceed? Something outside Themosis' website, some language selector there or just a branch in this repo? The community is getting bigger everyday, as well as the brazilian devs.

I'm testing a bit, and i can't seem custom fields to get to work.

My code:

 PT::make('brand', 'Brands', 'brand')
                ->setLabels(['add_new_item' => 'Add a new brand'])
                ->setArguments([
                       'public' => true,
                       'menu_position' => 20,
                       'supports' => ['title', 'editor', 'post-thumbnail'],
                       'rewrite' => false,
                       'query_var' => false
                ])->set();

        Metabox::make('properties', 'brand')
               ->add(Field::text('test'))
               ->set();

The metabox is visible on the edit screen, however the fields do not get loaded.
When inspecting in console we see a 404 error:
Error: Request failed with status code 404

It's trying to do a call to
http://mydomain.dev/wp-api/themosis/v1/metabox/properties?post_id=18 which gives a 404.

Any suggestions on how to fix this?

Thanks

It might be worth documenting the php console serve command, it's a nice alternative if you don't use Homestead.
Here is how Laravel documents it on their Installation page.

Developer can load an asset with an absolute URL if the asset is public or elsewhere in the framework than the default asset directory.

"More details on the Loop class here." links to https://github.com/themosis/documentation/blob/master/loop.md, which does not exist.

The current widget documentation is missing a call to the load() method in order to fully load the widgets defined in a custom location.

Hello,

The documentation says the minimal requirement for PHP = 5.4 (http://framework.themosis.com/docs/installation/), but the composer.json is set to >= 5.5.9.

What is the right value? @jlambe.

Reference: themosis/framework@66c1a67.

Add documentation regarding "facades".

I have a local version, that has its own compiled view such as:

/storage/views/c5060c6bbe13e3122cb409950a4ba0cdcc9a0f57.php
/storage/views/fff12666fb99ee057204a844e9ac50b527325a15.php

But when I load the repository in the server, files inside /storage/views/ are omitted.
I've seen this is an issue that is being addressed on future relases. So I copied the compiled views from my local repo into the server. But then I realized on the server's log, themosis is looking for a different compiled file of the views:

PHP Warning:  include(): Failed opening '/storage/views//84d3c649c9572fb2fa35f17823df232ec7101557.php'

This means the hash generated is different on the server than on my local version. I do not care to mantain the hash from local to the server. But I would like for themosis to recompile the views. Is there a command to recompile the views?

The configuration page has the following:

Let's grab all properties of the theme's theme.config.php file:

$all = Config::get('application');

Based on the explanation that comes after (the above code producing an exception in a fresh install) I believe it should be:

$all = Config::get('theme');