Thread Details
  • State Not Answered
  • Replies 9 replies
  • Subscribers 353 subscribers
  • Views 1524 views
  • Users 0 members are here
Forum Actions
Related

Custom Module create Manually stoped working.

Rodrigo Manara

Hi All,

I have 2 Modules create manually into a package , One works the other does not. This is the page I see when I trying to access the module, the strange thing these 2 modules were working fine, but after a reinstall one of the modules stoped working. 

I can see tables are created , I can see the modules Label displaying on the RolesModule, but it does not show on Sidecar. 

Does anyone knows what could be. 

Thanks

Rodrigo

Parents
  • 0

    No clue, but...

    I would:

    - Check permissions for the user (although if you are admin it should not matter)

    - Check the php log for errors

    - Check the Console for errors

    - Check file permissions.

    I use this from sugar root down to fix them all in one go (NOTE it's a pain if your uploads directory is too big and usually the culprit is in the directory I was working in or the cache folder so you can use them from whichever dir you want to rest)

    sudo chown -R  apache:apache * 

    sudo find . -type d -exec chmod 775 {} \;

    sudo find . -type f -exec chmod 664 {} \;

    - Do a QRR

    Hope you find the culprit

    FrancescaS

  • 0 in reply to Francesca Shiekh

    Thanks. I have look into the permission and all fine. when install via module loader,  where Sugar build the files? I can see call API using the normal rest without any customisations. I am sure is something related to sidecar.  

    Rodrigo Manara

    Sr. Developer

Reply Children
  • 0 in reply to Rodrigo Manara

    I believe the manifest will tell Sugar where to put the files.
    I've never built one but when I look at installable packages there is an

    $installdefs = array(
"copy" => array(
   array(
     "from" => "<basepath>/....",
     "to" => "..."
   )
...

    This maps the files from the basepath (which I believe is your php temp directory) to the application itself.

    I've never built a module from scratch without Module Builder, but when you install a module built with module builder it usually creates files in:

    modules/<module name>
    custom/modules/<module name>
    custom/metadata/<module name*.php>
    custom/Extension/modules/<module name>
    custom/Extension/application/Ext/TableDictionary/<*module_name*.php>
    custom/Extension/application/Ext/Include/<module>
    custom/Extension/application/Ext/Language/<*field_names*.php>

    There could be other code for subpanels in the case of relationships
    custom/modules/.

    On the database side there should be a module_name table, a module_name_audit table if you have any fields that were audited. There will be relationship tables to other modules which are usually named something like tableA_tableB_c when created via studio though the table names may be oddly abbreviated if you have long table names.
    Once you make changes via Studio and add fields you'll also have a module_name_cstm for any fields added after deployment.

    I'm not 100% sure this is a full list, but those are the places I would look... 

    FrancescaS