[GH-ISSUE #54] Problem with config generation #50

New issue

Closed

opened 2026-02-25 21:34:00 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 21:34:00 +03:00

Owner

Originally created by @mat-m on GitHub (Mar 27, 2016).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/54

Originally assigned to: @jasonmunro on GitHub.

After latest git pull (commit a9be0969fc), I have the following output :

# php scripts/config_gen.php

scanning module core ...
scanning module contacts ...
scanning module feeds ...
scanning module imap ...
scanning module smtp ...
scanning module site ...
scanning module account ...
scanning module idle_timer ...
scanning module calendar ...
scanning module themes ...
scanning module nux ...
scanning module developer ...
scanning module github ...
scanning module wordpress ...
scanning module history ...
scanning module saved_searches ...
scanning module nasa ...
sh: 431: 1: not found
sh: echo: I/O error
site.css file created
sh: 2906: 1: not found
sh: echo: I/O error
site.js file created
hm3.rc file written
creating production site

I don't know if it could be related to my setup or not (site.css is 0 byte)

Originally created by @mat-m on GitHub (Mar 27, 2016). Original GitHub issue: https://github.com/cypht-org/cypht/issues/54 Originally assigned to: @jasonmunro on GitHub. After latest git pull (commit a9be0969fc29fdf), I have the following output : `# php scripts/config_gen.php` > scanning module core ... > scanning module contacts ... > scanning module feeds ... > scanning module imap ... > scanning module smtp ... > scanning module site ... > scanning module account ... > scanning module idle_timer ... > scanning module calendar ... > scanning module themes ... > scanning module nux ... > scanning module developer ... > scanning module github ... > scanning module wordpress ... > scanning module history ... > scanning module saved_searches ... > scanning module nasa ... > sh: 431: 1: not found > sh: echo: I/O error > site.css file created > sh: 2906: 1: not found > sh: echo: I/O error > site.js file created > hm3.rc file written > creating production site I don't know if it could be related to my setup or not (site.css is 0 byte)

kerem

2026-02-25 21:34:00 +03:00

closed this issue
added the
bug

core
labels

kerem commented

2026-02-25 21:34:00 +03:00

Author

Owner

@jasonmunro commented on GitHub (Mar 27, 2016):

I'm not seeing this here. Do you have a css_compress setting set in your hm3.ini? If so that might be the source of the problem. We shell out to compress css with the command specified in that setting. If you do have it set to something, maybe try disabling it by setting it to false. Another possibility is file permission issues, but since the other files are created that seems less likely.

@jasonmunro commented on GitHub (Mar 27, 2016): I'm not seeing this here. Do you have a css_compress setting set in your hm3.ini? If so that might be the source of the problem. We shell out to compress css with the command specified in that setting. If you do have it set to something, maybe try disabling it by setting it to false. Another possibility is file permission issues, but since the other files are created that seems less likely.

kerem commented

2026-02-25 21:34:00 +03:00

Author

Owner

@mat-m commented on GitHub (Mar 28, 2016):

It was set to true and working. Setting them to false makes things work again.
Strange. Since I upgraded from Debian jessie to Debian wheezy, something might have changed in-between.

@mat-m commented on GitHub (Mar 28, 2016): It was set to `true` and working. Setting them to `false` makes things work again. Strange. Since I upgraded from Debian jessie to Debian wheezy, something might have changed in-between.

kerem commented

2026-02-25 21:34:00 +03:00

Author

Owner

@jasonmunro commented on GitHub (Mar 28, 2016):

Weird that it worked when set to true. We should definitely do some better error checking in the config script. If the output of the compression command does not return anything, we should issue a warning and use the uncompressed content. Should have a patch for that today or tomorrow. Thanks for the follow up!

@jasonmunro commented on GitHub (Mar 28, 2016): Weird that it worked when set to true. We should definitely do some better error checking in the config script. If the output of the compression command does not return anything, we should issue a warning and use the uncompressed content. Should have a patch for that today or tomorrow. Thanks for the follow up!

kerem commented

2026-02-25 21:34:00 +03:00

Author

Owner

@jasonmunro commented on GitHub (Mar 29, 2016):

The config generation script has been updated to check the results of the compression command, and use the uncompressed content if it fails. github.com/jasonmunro/hm3@07ff2131b3

@jasonmunro commented on GitHub (Mar 29, 2016): The config generation script has been updated to check the results of the compression command, and use the uncompressed content if it fails. https://github.com/jasonmunro/hm3/commit/07ff2131b380ab945750a259ed7a9f7577e8909d