maba

@soma thanks for the check on install/uninstall methods.

About the cache "problem": I can exclude any permission related issue for my installations. Tested on two different dev computer, MAMP, etc... 

In my case the two ModulesManager.cache files are both 283Kb and are generated in the right way.

One installation can use 350 limit (found 210 modules), other can use only 100 limit.

I'll try to remove all other modules and check it again.

Nothing.. 256Mb on new computer and same problem.

Hi Ryan, yes give the right process fix the "first" problem but it happens only after the PW update. In this case I didn't use export profile. 

Strange because both sites runs on the same MAMP machine with 128Mb for memory. And.. early no site given this problem, with limit set to 300.

Today I'll test these sites on another MAMP installation and 256Mb for memory on the first dev machine.

Thanks

After some tests I not found a solution but site 1 works with modules manager limit < 100 (350 on the other site).

Same dev machine.

Ok.. for the second site it works.

This morning I tried on first site with no luck.

Now on the second site and It works. But why the new installation does not work in the right way?

On the first site.. no. Now /setup/moduelsmanager go on timeout with no logs, with ModulesManager. Strange behavior, same MAMP machine.

And why it does not create the correct child on setup?

Thanks

For the first site I manually deleted the row and it was created by the installer again, but not the child under setup.

For the second site (cleaner situation) uninstaller/installer works well, child menu was not deleted.

Yes.. This happens on two different under dev sites.

Cache removed after uninstall and new installation. 

Another strange behavior.. after new installation I cannot see the new item under setup menu, but module is saved in module table.

Hi,

with the latest PW dev I've some problems with modules.

Go to /setup/MODULE and:

This page has no Process assigned.

This happens with "Export Site Profile" and "Modules Manager" for example. Not for all modules.

Uninstall and reinstall operations does not fix the problem.

Any idea?

Thanks,

Marco

EDIT: best answer for the first problem mentioned in post title.. other posts refers to a very strange problem on my installation.

It seems fixed now!

Thanks Adrian!

Adrian, thanks for the updates.

Unfortunately the ASM problem persists. I'll made other test with clean PW installation.

Catched! #Inputfield_submit shoud be #Inputfield_sumbit_save_module in ProcessCustomUploadNames.js:

$('#Inputfield_submit_save_module').click(function(e) {

Mmmm.. can the module have a problem with latest PW (2.3.7)?

No problem Adrian, it is under development.

Tested also with standard theme, Safari and Chrome on OSX.

No errors, the rule not appear, like screenshot.

It is only a screenshot.

Same problem here..

About new theme.. it is only a warning, you are right. 

In my case I cannot save the second rule.

How can I test it?

Thanks

Ok, ok.

The problem with this little fixes is that if I update my modules before your fix commit I cannot get the fixed version until a new ("major") version will be released.

It's not an issue but a warning. I commited an update that removes this already some time ago.

Ok, checked on GitHub and it is fixed.

So.. I think that is not up to date on modules directory. Should you change the version to update it on PW site?

Hi,

nobody with this little issue when use ModulesManager?

Warning: Missing argument 4 for ModulesManager::getActions(), called in .../src/cinema/site/modules/ModulesManager/ModulesManager.module on line 255 and defined in .../src/cinema/site/modules/ModulesManager/ModulesManager.module on line 469
 

Only with 1.0.9.

Hi,

in attach some screenshot about theme issues. Some problem with margin and padding.

You are right, line 249 is not about ruleData, but with last dev and the last module version I catch this warning.

New problem: I cannot add rules (see image). Problem with ASM select.

Ooops.. probably you know this issue.

Great job Adrian!

Very useful, and works well with CropImage module also.

Two notice when there are no rules:

Notice: Undefined index: ruleData in .../site/modules/CustomUploadNames/ProcessCustomUploadNames.module on line 249
Notice: Undefined index: filenameLength in .../site/modules/CustomUploadNames/ProcessCustomUploadNames.module on line 264

And.. something to fix with new admin themes.

I think that you have to use something like

$today = time();

or format $Dated with strftime() and $c->getUnformatted('Dated') with your formatted $today var.

Hi davo,

sure, it exists!

Have you tried today? See here..

Another little bug with the new themes: in Templates->Advanced->List of fields.. if we use 

icon-time title year

the result is

ICON titleyear

no comma and space between fields.

Yes, I confirm that the problem is generated by round(), floatval() and (float).

Float values are vulnerable to rounding errors are they have limited precision. PHP (locale ) and MySQL issue.

In my case I use it for currency (only to store prices, no other operations), so.. How do we store currency in PW? A new FieldTypeDecimal or similar with DECIMAL type in MySQL?

Ryan, last commits solve my problems also! 

Thanks!