No not yet, I have been on holidays too. And when I came back Crisu83 changed the whole Bootstrap module of his. There had been a new version of Twitter Bootstrap then, the new module is build on that new version I suppose.

Do you use the new or the old crisu83.bootstrap in Phundament?

==============

I hope you can help me with the following question I have: can you make submenu-items within P3 Content Management functionality? I can make a sub-item in the Sitemap (P3MetaTree) but it doesn't appear in the BootNavbar structure. Is there a way to do this?

So you should be able to create menu items with every menu node, although you'd have to wrap it into some code, like getting your first level nodes manually and then use the method above to get the submenu items.

I really find the new structure much more usable, but anyway, you should be able to use any directory structure - that's a feature of Phundament.

How do you do your updates? Do you update phundament/app itself or are composer updates the problem?
Composer should not be affected by this change, besides that you have to do some more imports now, but that's the only way to keep it totally flexible.

btw: you can find the classic structure in the yii-webapp branch, although I've moved everything to protected there, because of security issues.

Thank you for your message, you've got a personal message back from me.

In the interest of helping the community also, I ask some more questions here. Perhaps it helps others... The latest layout of P3 I really like! You have used the Bootstrap layout in the views, it looks very clean and nice.

The PageMeta model has a lot of properties and a few I don't understand the function of. Looking at p3pages/models/BaseP3PageMeta there are the following properties:

Thank you for your message, you've got a personal message back from me.

In the interest of helping the community also, I ask some more questions here. Perhaps it helps others... The latest layout of P3 I really like! You have used the Bootstrap layout in the views, it looks very clean and nice.

Thanks. I splitted the themes in a public part (www/themes) where all the js- and css-files are.
And defined the viewPath in a protected directory.

ametad, on 02 October 2012 - 06:30 AM, said:

The PageMeta model has a lot of properties and a few I don't understand the function of. Looking at p3pages/models/BaseP3PageMeta there are the following properties:

The MetaData models store data, which is common for different models. The data is partially auto-generated with P3MetaData Behavior
And (tbd) there should be a widget which handles the meta-data.

What about the CKEditor templates? I am trying to locate the right file wich includes the templates for the editor. Isn't it the cktemplates.js file? In this somewhat older installation there I can find this file in these directories:

extensions/phundament/themes/p3bootstrap/ckeditor/cktemplates.js

themes/backend/ckeditor/cktemplates.js

themes/frontend/ckeditor/cktemplates.js

But whatever I do... it doesn't change the templates?! I also - in all cases - removed the /assets folder with cached files. What file has to be changed?

I thought that I could do a 'composer.phar update' to let it download all latest versions of the included repos (from Github and/or Bitbucket or where ever). But how does this work if the directory structure is changed all of a sudden? Or is this not a problem? What do you mean with an import, is that the download of a particular repo?

No, shouldn't be a problem. The new structure only affects new P3 installations - in theory

You shouldn't clone the repo for a new project - download a tagged version, they contain "stable" releases.
At least don't git pull from phundament/app.git.
This repo does only contain the config files for Yii and composer, if you change those you're very likely to run into problems.
It makes sense to just update the config/ComposerCallback.php file and adjust your composer.json scripts, but don't change vendor-dir.
But, even if you'd do so - you would only download the new files.

For the packages you may have to adjust some aliases and import though. That's because I removed paths like 'ext.crisu83.yii-bootstrap.widgtes.TbMenu' with 'TbMenu', otherwise you'd be able to change the vendor-dir location.
But you can stick to 0.6.* versions of p3widgets, p3pages, .... but that's just a minor thing - require them in comopser.json and run comopser.phar update.

Best regards,
schmunk

PS: But cloning the repo would the right way to update P3 with the yii-user changes you mentioned I think it would be just an update of composer.json - I should do that on packages.phundament.com - and config/console.php as the migrations would now be taken from the module, I have this one somewhere as a todo.

[edit]
Or have a look at your generated source code, search also for 'templates_files'

Thanks, found it! I searched the generated code and there it stated the location. One thing I had not done was clearing the cache of the browser. After 1) editing the cktemplates.js file in the theme folder, 2) clearing the Yii cache and 3) clearing the browser cache it worked like a charm.

Your previous post about the update of Phundament I am still processing. But it is helpful already.

Another thing I came across is an conflict between certain Javascripts, one from the UserModule and one from the P3WidgetsModule. You can see what the problem is when you make a new ProfileField in the UserModule. Try to do this with an user-account with only enough rights to access the UserModule controller actions (NOT with access to the P3WidgetsModule controller actions).

When you choose a FieldType, certain params get an pre-defined value. Choosing VARCHAR sets the FieldSize to 255 e.g. and FieldType INTEGER gets a FieldSize of 10.

In the ProfileFieldController the public function registerScript() has the following JS which handles mentioned behaviour:

The problem occurs when the account has the rights to edit a P3 Widget (Translation) also. Another JavaScript handles the display of the buttons that appear when you hover over a P3Widget. Those buttons give access to edit the content etc.

I have not much knowledge of JS yet, so I don't see why those two scripts don't work together. But I notice that the pre-defined values for all kind of params of the ProfilField are not set automatically any-more.

This brings me to a conclusion that could work.. Because the yii-user module of Mishamx is hardly updated/-graded you could fork it and distribute it for a P3 installation. Then change the paths once to be more flexible. I think a module should be written to be as flexible as possible so it can be placed wherever you like. Some people will place it in the extension folder, or in the modules folder, or as you do now in a folder called 'vendor'.
Perhaps it is best to send in a pull request of yii-user to mishamx with some little changes that make the module more flexible.