tzyganu / umc1.9

New Ultimate Module Creator for Magento 1.7 +

Ultimate Module Creator 1.9.6.0

Notice

Because of lack of time, motivation and because Magento2 is already a mature platform, I'm deciding to pull the plug on this module creator.
There will be no updates, no new features.

Feel free to fork it, make it better and redestribute it.

New Ultimate Module Creator for Magento 1.7 +

This is the new version of Ultimate Module Creator.

This should be the version 2.0 of the Magento extension but I'm keeping this version for the Module Creator for Magento 2.0.

Backwards compatibility has been broken.

If someone wants to help with the testing please submit any bugs, improvements or feature requests here

Also any good code is welcomed.

Note For the rest of the document UMC = Ultimate Module Creator

Documentation can be found on the wiki pages.
The documentation includes a list of features and release notes

umc1.9's Issues

Dropdown manual list seperator

Personally I feel using the pipe | operator to separate the list items a bit 'counter intuitive' since the textarea is so big, I've nearly every time used newlines on every first try, to remember it doesn't work that way. I don't know how many people submit lists of 50 or more items, but personally I think you might wanna abstract into a piece of dynamic db driven list if your static lists are becoming that long. So while pipe might be good (due to width) for text_fields_, they seem less appropriate to use inside a multirow/column text area unless frequently populated with a large amount of items.

Allow to kickstarter Module without entities

Often I come across of using silksoftwares Script to kickstart a Module which just does basic things (like listening to an event and do X) and therefore it does not contain any entities.
With this module however I am forced to setup entities which I wont use in the end anyway.

Do I miss something or does this module just dont allow creating modules without entities?

Customer relationship

It would be useful to be able to link entities to customers the way you can already do with products.

Fatal error: Call to undefined method Varien_Io_File::filePutContent()

Magento ver. 1.9.0.1

Fatal error: Call to undefined method Varien_Io_File::filePutContent() in /home/box/public_html/dev/app/code/community/Ultimate/ModuleCreator/Model/Module.php on line 487

Unable to create or edit existing modules I've made with this before. Not sure it is related to a recent update I did on this extension or the moving around from sub-domain to main domain and back again with Mage install, but both main ans sub are now reporting this upon hitting save.

Missing translation for label "<label>Use Breadcrumbs</label>"

The label "Use Breadcrumbs" is not written into the translation file.

app/code/community/Ultimate/ModuleCreator/Model/Entity.php:1262

Relation between more than one entity

Hi,

It seems that I can't create a relation between more than one entity within the same extension. When I save the selected relation between entities, unfortunately nothing happened when I re-open the 'Entity Relations' tab.

With just two entities, everything works well.

Thanks,

Michael

Associated products entity anchors missing

This is another 'workflow' slash navigational issue/proposal. I've attached the screenshot. Notice in those case, the product details cannot be navigated to, due to missing anchor <a href="..."> element+attributes not being there as visible in the chrome source view.

Currently it checks/unchecks the boxes.

Minor nuisance

Hi again. Sorry to keep bothering you with nitty gritty stuff.... (wait for it) ,... but, I was wondering if you could toggle modulecreator-toggle open class on the particular field/entity which contains the missing or incorrect filled in form values which don't pass validation. If it's not a lot of work (meaning if there is some data structure holding the logic which HTML for input/field goes where) - I don't have enough (any really) hours in development on backend Adminhtml so I really wouldn't know how these things are done/grouped in what collections. Anyway, marked it minor for a reason, discard if you like ;) Cheers, and thanks.

Rob

Entity field notes escape single quotes

Currently, if I use a single quote in the notes field, it breaks the admin backend of that entity since the quote is taken in as code... Sanitize input perhaps?

Cheers, and keep up the good work. I've got a few comments and suggestions once this deadline passes and I deliver 👍

Use (firegento) magento-composer-installer?

Hi, I was wondering. Would you or have considered using composer, in particular the (firegento repo) magento-composer-installer convention/tool for UMC?

I assume you heard of it, but since your project still is missing a composer.json file, it might very well be possible to have escaped your attention.

In terms of automated (symlinkfarm) dependency management/resolution and deployment, also with respect to the better filtering of Magento specific libraries, I believe it's by far the superior (workflow) tool since it leverages Connect 2.0 auto-generated packages and package.xml, modman mappings and composer files all in one.

Currently I have to reference your extension inside a "package" inline definition of the modman desired schema, automated resolution would obviously be the prefered method hence this note :)

Cheers and keep up the good work!

Rob

Problem with 'Link "many to many" with category'

Hi,

I have a problem when choosing 'Link "many to many" with category' on the category-tab of an entity.

All other dropdown fields on the tab are set to 'No'.

After installing the created extension the following errors occur:
When going to "Catalog/Manage Categories" a white pages appear.
In the log the following error is added:
PHP Fatal error: Call to undefined method [NAMESPACE]_[MODULE NAME]Model_Resource[ENTITY CODE]_Collection::addCategoryFilter() in [...]/web/app/code/local/[NAMESPACE]/[MODULE NAME]/Helper/Category.php on line 52

When I edit one entity of the created extension I can't add any categories.
When I click on the tab "Associated categories" the content area remains empty.
In exception.log I get the following Error:

I have tested it on two different magento systems (UMC 1.9.4.1 and Magento 1.8.1.0) and the problem occured on both systems.

Regards
Lars

Can we have search form for entity OR can we include terms in main search form of magento

Hi Marius,

Recently I got requirement to have search functionality in our custom module entity. So, I suggest if we can implement search form functionality then it would be great.

Module can have separate search form OR some great opportunity to manipulate main search to look in our module tables. ( just like in admin global search )

Can we implement it ?

Thanks

route and frontName settings

Could you add a "route" setting that would override the use of the lowercased modulename, and a "frontName" setting that would allow independence with the route value ? Thank you !

Problem in installation from magento-connect

When I trying to install this extension from magento-connect I get the below error.

Checking dependencies of packages
Starting to download Ultimate_ModuleCreator-1.9.4.4.tgz ...
...done: 290,638 bytes
Installing package community/Ultimate_ModuleCreator 1.9.4.4

CONNECT ERROR: Failed to open file D:/xampp/htdocs/magento\downloader.cache\community\Ultimate_ModuleCreator-1.9.4.4\app/code/community/Ultimate/ModuleCreator/Block/Adminhtml/Modulecreator/System/Config/Form/Fieldset/

I checked that location and there is no files. And lot of files and directories are missing.
And the .tgz file D:/xampp/htdocs/magento\downloader.cache\community is corrupted, when I extract manually lot files are missing.
And this is second time I'm getting this error (3 month before I have faced same issue).

I can install this extension by manually only (using freegento.com).

No xml and sql files generated

If this module can generate xml and sql files for the module , i've tried twice and try to install at once or unzip from zip file to the instance, but either way the module's xml and sql not generated.

Improvements

As I told you in Magento StackExchange, I missed some features in your ModuleCreator extension, all for admin interface.

In a master/slave structure of entities, instead of creating a menu access for each one I wish your module could show the slave in a grid in the edit tab of the master.

Entity fields could take default values.

Ability to define select(dropdown) fields in a master/slave structure of entities.

Set default values for EAV entities

When creating an EAV entity in the generated module in the backend, the form should be filled in with the default values for the attributes.

This is extracted from #7.

Optional enable/disable status

When creating a bunch of entities, only one of which is the front-end entity, it tends to only make sense for that single front-end entity to have enable/disable as an option. Along with the mandatory name field, it is the enable/disable status that I find myself having to manually strip out from most entities. Didn't this use to be an option?

Installing newly created package

When I try to install a newly created package via the magento connect manager on magento 1.8 I get "CONNECT ERROR: Unsupported resource type"

Renderers and parent/child relations?

Would it be desirable/possible to perhaps add something of a entity hyperlink renderer for adminhtml grids and in particular I mean the parent ones in the children?

I don't know if Magento has something like this built in (hyperlink column renderer), but one thing I think is missing is e.g. like this screenshot below. The agis-sv2-14-1 is the parent name (the enforced one) and it would be quite useful to have say a agis-sv2-14-1 hyperlink in the child table (as edit has in the screenshot).

Now this example uses few parents and many children but this may vary in cases - a few might have many and many may have less (^^) - but it more or less boils down to any use-case I can think of which takes the child as a starting point and then wishes to look up something in the parent, it is always a manual process of copying (or remembering) the name and going to the grid for the parent and then filter those:

Which, I'll admit, isn't that big of a deal but still might be 'user-friendly' or convenience enough to like (or hate to miss if you have to do this all the time).

Nor does the dropdown (details of child) really help in this case (vis-a-vis would adding the parent as a tab to the child details be an option? I guess an entity can have multiple parents can't it? Perhaps then it might even be more useful or... hard to do, can't really judge that atm).

Thoughts?

Cheers,
Rob

API: store scope, pictures...

Hi,

I can't find out how to use the API generated for EAV entities. It works fine for simple entities, but it seems to me that :

• Pictures/files linked to entity must be handled manually, as according to wsdl the picture/file attributes are expecting a string. This can be achieved without too much work in local context, but this kind of defeat the all point of the API.
• There is no way to handle values for specific store context. the generated api.xml mentions a "currentStore" endpoint, but none is actually implemented. I've tried to add it manually from what exists in Mage/Catalog/Model/Api/Resource, but with no success so far.
  In case of a multilingual store, this leaves half the content to enter by hand :-/

Have I missed something?

Module suite

Ever read this article? I found it enticing and wondered if we could use this to hook up UMC modules with each other? To create a 'domain' of grouped entities in modules. It shouldn't be too hard to then define relations between entities in those modules.

Any thoughts?

Entity relationships not saved

Entity Relationships are not saved. Next time I check the module they are not there. And I get the feeling they are not created because I dont see parent key field y children table

Flash message initialization missing in frontend controllers

In frontend controller's indexAction() the following lines of codes are missing:

$this->_initLayoutMessages('customer/session');
$this->_initLayoutMessages('catalog/session');

Category "many to many" and category "options source" no result in 1.9.0.1

Hi Marius,

Thanks for the beautifull module creator in pure Magento. Perfect source. Great job. But I think that's not the first time someone told you. I hav the opportunity to build a new application in Magento and I'm getting a quick start using UMC.

I created a entity and tried to link it to the catalog table with the options you have in UMC. The many-to-many and the option-source method both didn't work. The many to many refered to a tab/categories.php that doesn't exist and the option source is reading a $this->_source that is empty and then reades the default source for the ->getAllOptions.

The product many-to-many does work btw.

Extra info is that I didn't try to link the categories to the entities the first time I created the module. But after updating the UMC adding the link I cleaned the database (older db version without this module) and removed all the old modified files.

Maybe you should try yourself with the Magento 1.9.0.1. If it works for you please let me know. But it looks like a bug.

Thanks in advance.
With kind regards,
John Verzijden
Webverzorgers

(suggestion) Manage translations for records through scope

Hi all, I have a suggestion, I have tried to do it but I have not the necessary knowledge

Add functionality translations give the records to avoid duplicate records for each language, as it is done with the products and product categories:

note: my store has the languages​​: Spanish (default) and English, Via scope to give the English translations for each category

thanks

Naming of predicates generated for boolean fields

Hi again. First off, let me thank you for all the hard work and - as I noticed actually - incorporating some of the minors I posted earlier. I actually noticed a thing with the naming convention and checked against the core. Would it be in line with predicate naming convention to change e.g.:

getUseBreadCrumbs

to

isUseBreadCrumbs

Not a biggie but still worth the request imho :) Btw, UMC is saving me tons of work - cheers for that and I hope to free up some time soon to become a bit more involved in the community and see if I can lend a hand here and there instead of being lame and asking :P

Rob

Problem with saving form / field values

First of all, thank you for the great extension!

I noticed that when I create an extension... It works just fine, but when I edit it and add other attribute fields these new fields dont work.

Basically I do these steps:

1. I create extension, prepare all fields, click on Save.
2. Download extension and install it on website. Everything works fine.
3. Go back in Module Creator, add some new fields in extension.
4. Uninstal the extension from both folders and Database
5. Instal a new version of extension with new fields.

On the website, in extension, I do see these new fields in both backend, and in Database as well... but when I click on save, the values are not saved, and I just get empty fields. in DB the values are NULL.

I tried different field types, Image, WYSIWYG, Text etc...

Always the same issue, after I add new fields on already created extension - the values dont get saved.

I use UMC 1.9.4.1 with Magento CE 1.9.0.1

Regards,
Archie

OptionArray or 'poor man entity relations'?

Ok I've shortened the OT a bit to provide a more terse explanation of the initial idea.

1. take a entity/object of the kind which implements toOptionArray()
2. have it populate multiselect list with entities
3. store those entity values as a comma separated list of integers to explode after retrieval
4. provide a 'templated' string URL source which will interpolate the integer values at desired position
5. render the final list in a columns as <a href="http://domain.tld/store/domain/entity/id/{{.}}/view" ...>..</a>, <a href="" ...> elements

A few comments, pro's and con's noted:

• we will definitely not need all elements with toOptionArray() - checked with grep -ERn 'function toOptionArray(). Some interesting ones are listed below.
• since we do not want to display all varien collections that have optionArray but also do not want to exclude any e.g. community or local entities
• due to the Magento core override system functioning this wouldn't pose a codepool problem since local always wins and should be used anyway - retrieval is dynamic anyway so whoever wins, wins.
• the major cultprit, as is now with option array, is any syntax errors, typos or non-existing attributes reference - which of course will expose itself during script interpretation only given its dynamic nature - and as such, nothing we can do about anyway to prevent people from making mistakes. This is significantly different from the rest of the module creator in the sense that you are in full control of the generation process.
• agreed that the entire list as selection (of toOptionArray() function definitions) would screw up the intent (80% is garbage anyway) - wonder if anything weighs up the trouble of hinting the user of any potentially interesting option arrays

That last point made me think on whether it would need to be multi-selectable values/controls and if that needs to make sense.

For example: while it might make sense to apply Mage_Api2_Model_Acl_Global_Rule_Privilege (array of class constants) multiple times on a custom entity, it would be much of a corner case, perhaps only if the entities are constraints or rules applied on entities which would have properties exposed via REST, but highly unlikely. Also multiselect of e.g. Language/Collection items wouldn't make much sense unless they'd be applied to individual entities, not as a whole on a single entity. That is to say, if the custom entity would be an abstraction of pages and that particular field would be the languages available to translate content... anyway you get my drift. Rather far fetched use-cases imho.

A few indeed, should probably be of more interest but, again, one doesn't exclude the other per se.

• Orders
• Order Items (very desirable as Mage doesn't allow much interaction afterwards with those does it?)
• CMS Pages
• Order status
• Websites/stores
• Templates

Orders problem is: Magento doesn't really support it (which doesn't mean they can't be included via simple integer to route URL interpolation and im-/explosion of the elements

Downloadable/Model/System/Config/Source/Orderitemstatus.php +36
Adminhtml/Model/System/Config/Source/Order/Status.php +43
Sales/Model/Resource/Order/Status/Collection.php +49
CatalogInventory/Model/Source/Backorders.php +29

Composing orders programmatically is hard, but retrieval relatively very easy. Same goes for CMS pages and a few other things so yeah, I guess they may be good candidates.

[feature] create upgrading script

If I installed the UMC1.9 on the system and want to add new field , what about to add upgrading script to it(once i set a version greater than old one)?

Child Collection

This feature request is migrated from tzyganu/moduleCreator#10. It is not implemented yet in this version either.
Original issue posted by Detzler:

imagine the following domain:

• ParentModel
• ChildModel (1 to n)

There is no method in ParentModel to get all ChildModels, also there is no method in ChildModelCollection to set a ParentModelFilter to get all ChildModels of a specific ParentModel.

Small bug in processing "Show associated entities on category page"

Hello again from your humble assistant)

As i see, on this line correct method in condition must be a "getShowOnCategory", not "getShowOnProduct".

This line of code:
https://github.com/tzyganu/UMC1.9/blob/master/app/code/community/Ultimate/ModuleCreator/Model/Module.php#L1649

Could UMC handle int field not to unsigned as default?

I found one issue that UMC create int field default as 'unsigned'.
But sometime we need a field to show negative number. How about to let user to select the type if they want the unsigned?

Installation problems

Following a question I had done in Ultimate Module creator FAQ, I have created a module and downloaded it from the admin site. Nevertheless, some files are created with a wrong extention: "ph" instead of "php" and "phtm" instead of "phtml". One of them is the installation php file aiming to create the db.

By extracting the files in the magento folder, the module doesn't work. The way it gets to work is if I manually rename all extentions and create the database tables by hand, since the installation script is not executed.

The problem is that the module doesn't work fine, since I am able to create a new entry of the entity I have created and then I cannot insert or update (keeps going to the first id). I believe it is an installation problem because of the manual corrections I did.

Note that I work in a windows environment and that I can send you the generated module if you wish.

Thanks in advance,
Nikos

List Block class ->addFilter() not working

In List block class generated by the extension:

public function __construct(){
        parent::__construct();
        $modules = Mage::getResourceModel('namespace/module_collection')
                        ->addStoreFilter(Mage::app()->getStore())
                ->addFilter('status', 1)
        ;
        $modules ->setOrder('entity_id', 'asc');
        $this->setModules($modules );
    }

In above code,

->addFilter('status', 1)

should be

->addFieldToFilter('status', 1)

ui issue

Tagging releases

Hey,

Just a quick note while I was writing up a few other plugin developers as well. I noticed quite a few people (including myself) fail to sometimes get the whole Composer shenanigan around versioning packages, but from what I understand, its very much essential to use tags for releases if you wish to use composer in a effective (non-breaking) production setup. The problem is addressed here quite well with regards to the rationale behind it.

Thing is, stupid as it is, one is discouraged to manually version composer.json file but, ultimately, composer does not offer a easy (cli) way of finding out what the current release is. One has to manually check packagist or github tags and, if not present, ultimately reside to the much less favored dev-master version. This will eventually cause breaking of the composer update when version increments take place and branches named as 1.9.x should always be aliased to the relevant dev-master. Using tags is way better since it is just the snapshot instance you want to prevent any mismatch in dev-master versions between author and user.

Also, I should note, that I quit using npm cson for conversion of the (wagner) composer.cson to .json.

Instead, I would suggest to use the much better supported/developed npm i -g season package and one can keep the file named composer.cson which after csonc composer.cson will generate the .json file. Checking with composer validate is always a good idea (which is when I noticed some packages had wrong versioning) and circle is round again. :)

Inconsistent registry naming

In frontend controller, I can see different registry names.
For example:

Mage::register('current_module', $module); 
Mage::register('current_namespace_module', $module); 
Mage::register('module_data', $module); 

Notes form fields are not displayed

Today start to use the version 1.9 and it is amazing, Building my fisrt module i realize that the notes for the fields are not displayer

I realized that the structure is not equal to version 1.6 which was the first to use, take a look at app/code/community/Company/Namespace/Block/Adminhtml/Advice/Edit/Tab/Attributes.php

and I realized that attr is read and send the form directly to the constructor

$attributes = $this->getAttributes();
foreach ($attributes as $attribute){
    $attribute->setEntity(Mage::getResourceModel('digisolution_chefevolution/advice'));
}
$this->_setFieldset($attributes, $fieldset, array());
![magento admin](https://cloud.githubusercontent.com/assets/5633504/2598502/19e5a57e-bac9-11e3-87f2-210ef5896ed3.png)

Mymodule.xml

![screenshot from 2014 04 02 20 13 19](https://cloud.githubusercontent.com/assets/5633504/2598504/1f3a18d4-bac9-11e3-8a84-a19fb8fbe73d.png)

Thanks!!!

Error : Front controller reached 100 router match iterations when visit entity page on front side.

Hi Marius,

I have used UMC in my project to make chefs and have associated them with products.

I see this error when I open entity view page( In my case chef page ) on front side. I have followed suggestion by @zerkella on this link : http://stackoverflow.com/questions/6262129/magento-front-controller-reached-100-router-match-iterations-error to debug.

I see my system.log file is filled with Iteration 1 to 100 with this same error below.

2014-10-01T11:03:46+00:00 DEBUG (7): - Iteration 100
2014-10-01T11:03:46+00:00 DEBUG (7): Request: [path_info=/christian-schweiniger][module=chefs][action=view][controller=chef][controller_module=][route=lekkerei_chefs]
2014-10-01T11:03:46+00:00 DEBUG (7): Matched by "lekkerei_chefs" router, class Lekkerei_Chefs_Controller_Router

I see controller_module is empty, but I don't know why. I have not made any customization with my module.

Please help me to solve this error.

Thanks

RSS helper url function name

I found a litle issue in the RSS url function name. The toHtml() call this helper function as:
$url = Mage::helper('{{namespace}}{{module}}/{{entity}}')->get{{Entities}}Url();

The solution maybe:
etc/source/app/code/Helper/Entity/050_rss:
.- public function getGetUrl(){
.+ public function get{{Entities}}Url(){

Uninstall scripts

I was working on some concepts in UMC and decided (since I needed to see what code it would generate etc) at some point to install. Then I manually (can we add auto-incremental major, minor, patch? Also 0.0.1 should probably be 0.1.0 since a version 0 can't really be patched after all). That is, if you want to enforce semantic versioning, which I figure not everyone may like... anyway, down to the real observed problem. Not sure if reported/realized but I just found out after 0.0.1 the application wouldn't install (that is while the module itself is set on 0.0.3 now, and has some significant changes to 0.0.1) and now the download SQL uninstall script has unknown tables, attributes in it. So I checked the var/modulecreator/package folder but... oops: only 1 version is kept the whole time? Perhaps a versioning history as Magento SQL scripts (should actually, not always) work? Seems like a safe thing to do, for now I'll remind myself to keep doing this manually each upgrade/patch.

Missing single quotation mark in _filterDates() parameter $dateFields

I have created two date fields. There is an missing single quotation mark for the $dateFields parameter in the method call _filterDates() in the saveAction() of an Adminhtml Controller (see attached Screenshot).

form add/edit translate labels

Hi, I just noticed that the form add/edit entity in the admin panel does not load translation labels located in the csv file extension

One more bug in category many-to-many relations

We can assume this is a continuation of the ability to make some of the recent bug with categories: #51

The bug occurs when you are in the UMC are ticked off that allows you to assign catalog categories with the entity on category editing page.

This block is not included to module archive: "model_resource_entity_collection/.../080_category_relation" in "umc_source.xml", but it a needed to include :)

P.S. Many thanks for developing and support this module.

Misspelled word in error message

Change the word deleteing into deleting in line 30 in
/app/code/community/Ultimate/ModuleCreator/etc/source/app/code/controllers/Adminhtml/Module/EntityControllerFlatNotTree/110_center
and
in line 12 and 16 in
app/code/community/Ultimate/ModuleCreator/etc/source/app/locale/020_entity

Associated Product Grid Paging When Editing Entity

I've created three separate modules with UMC but have just noticed a problem with the product grid paging in the "Associated Products" tab in all of them. It happens only when I am editing an already created entity. If I click the "Reset Filter" button to see all available products, I get the first page of products, but if I click the icon to go to the second page, the product list resets to showing just the selected products. Thus I can never page to the second page of products.

If I click "Reset Filter" and search for a particular product, I can find it and select it, but "Save" or "Save And Continue Edit" will not actually save the association.

I have matched my dev and production environments as closely as possible, but the problem only happens in production (the only real difference I can see is that dev uses php-fpm and production uses FastCGI for php, but the php setting are nearly identical). I thought it may be a session issue, but I can page through products just fine in the "Manage Products" section. I don't see any JS errors or anything in the server's error logs.

EDIT
Not sure if this is helpful, but I've noticed one differentiation in the AJAX URLs between the dev and production servers.

Dev:
/admin/albums_album/productsGrid/id/2/key/xxxx/filter//page/2/?ajax=true&isAjax=true

Production:
/admin/albums_album/productsGrid/id/2/key/xxxx/page/2/?ajax=true&isAjax=true

The production server leaves out the "filter//" which appears in the dev URL right after the key value and right before "/page". If I cut-and-paste the partial dev URL and use it on the production server, the pages loads the correct info (sans any styling) so my problem may be related to the AJAX URL. I've been poring over the code with no luck.

Docblocks and project + entity documentation

I'll skip this for now, after countless rewrites and insights, abstractions and adjustments, I need to think about this some more.

Plethora of install issues

I have found some previous information about similar issues as mine, but nothing here and nothing that has solved anything.

First off, from a completely fresh Magento install, I am unable to install the module from the CLI using:

./mage install community Ultimate_ModuleCreator

I have also tried installing the file directly using:

./mage install-file path.to.the.file.tgz

Both times I am getting the following error:

Checking dependencies of packages
Starting to download Ultimate_ModuleCreator-1.9.4.1.tgz ...
...done: 290,426 bytes
Installing package community/Ultimate_ModuleCreator 1.9.4.1
Error:
install: Failed to open file /usr/share/nginx/html/downloader/.cache/community/Ultimate_ModuleCreator-1.9.4.1/app/code/community/Ultimate/ModuleCreator/Block/Adminhtml/Modulecreator/System/Config/Form/Fieldset/

As suggested in other references to a similar problem, I've tried simply installing the files through FTP by copying them over to my install. Initially the module makes no appearance in the backend (System>Config>Advanced>Advanced does not recognize the module XML) so after adjusting permissions to reflect generic Magento permissions, I simply get an empty white page in both front and backend and no logging is happening. The only way to resolve the issue was to remove Magento files and database and start from scratch.

I know I've used the module previously on a basically identical server setup. Additionally, I have tried this now on several server setups (nginx and Apache with different configs) and every time I try to install the way it should work (via ./mage install) I get the same errors. Every other module I have tried to install the same method has worked flawlessly.

Has something been changed in a recent update to this module to cause it to break? Also, is it necessary to package the module with all the files that are found in app/etc/source?

Gzip/Tarball compression (minor)

Just thought I'd let you know in case you hadn't found out yet:

tar xzf MyVendor_MyPackage.tgz
tar: Dit ziet er niet uit als een tar-archief
tar: Alles tot aan volgende kop wordt overgeslagen
tar: Gestopt in fouttoestand vanwege eerdere fouten

Translated: "doesn't look like a tar archive, everything up to the next head will be skipped. Stopped in erroneous state due to earlier errors."

Unpacking using first gunzip and next tar xf does work however so this might be a script generation related thing (got a related issue with my piping mysqldump to archive - or atleast me wanting to do it straight away streaming data, since tar can't handle that I think).