How can I change a configuration variable through the backend panel in Typo3?
I need to set this line in the global configuration from
$TYPO3_CONF_VARS['FE']['activateContentAdapter'] = '';
to
$TYPO3_CONF_VARS['FE']['activateContentAdapter'] = '1';
Do I have to use the installation tool ?
In the backend, go to Install Tool > All Configuration
Expand $TYPO3_CONF_VARS['FE']
Check [FE][activateContentAdapter] = 0
This solves the distribution.png issue.
In TYPO3 6.2 the contentAdapter is active on default, if not explicit set to FALSE in your LocalConfiguration.
Related
During the upgrade process on odoo.sh on branch BrStaging, there are errors in the log panel. Some obsolete custom Modules or Views are the cause of these errors. To disable or uninstall them, we have to use SQL queries because we cannot enter odoo which cannot start:
My Try: using in Odoo-sh> SHELL-Tab, the shell command : psql:
To disable a view
UPDATE public.ir_ui_view SET active = false WHERE id = 10381;
To disable/uninstall a module
UPDATE ir_module_module set state='to remove'
WHERE name in ('my_custom_module') and state='installed';
...have tried that request too:
UPDATE ir_module_module set state='uninstallable'
WHERE name in ('my_custom_module') and state='installed';
...But it does t work: after a commit or restart (command: odoosh-restart) the related error still remains!
How to disable a view and uninstall a module during the upgrade process from v13 to v15 ??
The solution, I have found is using a pre-migrate.py file into one of my custom module : my_custom_module/migrations/15.0.0.0.0/pre-migrate.py
which contain the Sql query that i need to execute, to correct the upgrade-log-Error:
def migrate(cr, version):
# TO CORRECT UPGRADE ERROR 1 : Element '<xpath expr="//xxxx">' cannot be located in parent view
cr.execute("""
update ir_ui_view v
set inherit_id = NULL, mode='primary', active = false
where
v.id in (10563,10539)
""")
How can i add configurations to start a kernel via jupyter_client.manager.start_new_kernel() without setting up a default configuration file in .ipython directory? I want to set shell colors to 'NoColor' without setting up a config file and initialize specific formatters.
This is equivalent to the following config file:
c = get_config()
c.InteractiveShell.colors = 'NoColor'
This worked: manager.start_new_kernel(extra_arguments=["--colors='NoColor'"])
I have TYPO3 (4.5) installed and a running project. The RealUrl extension is installed and enabled. Everything works as it should. For a proper user of the RealUrl extension i needed to add a few lines of code to the main template.
config.simulateStaticDocuments = 0
config.baseURL = http://www.example.com/
config.tx_realurl_enable = 1
Now i need access to the site by different sub-domains (eg "www1"). I tried the code below, but it is not working. I am not sure about the script i came up with.
host = example.com
[globalString = IENV:HTTP_HOST=www.example.com]
host = www.example.com
[globalString = IENV:HTTP_HOST=www1.example.com]
host = www1.example.com
[global]
config.simulateStaticDocuments = 0
config.baseURL= http://{$host}/
config.tx_realurl_enable = 1
Is this sufficient to keep the system running?
Variables need to be registered at the constant part of the template. TypoScript is no scripting language, but a treebuilding definition set.
I suggest to skip variables alltogether and instead append the following to the end of your TypoScript.
config.baseURL = http://example.com
[globalString = IENV:HTTP_HOST=www.example.com]
config.baseURL = http://www.example.com
[globalString = IENV:HTTP_HOST=www1.example.com]
config.baseURL = http://www1.example.com
[global]
Additionally you should use config.absRefPrefix instead of config.baseURL.
How do I set the application_name as defined here http://www.postgresql.org/docs/9.1/static/libpq-connect.html, in Laravel? I see that you can do "SET application_name = 'application'" but this does not work for me. I also tried setting it in the app/config/database.php file in the 'connections' array. What am I doing wrong?
You have to put in the env file (/.env) the variable regarding the application name named DB_APPLICATION_NAME = ;
And you have to specify the following:
Form Laravel version 5.5 you can add this row to the file /config/database.php at the bottom of the postgresql connection.
'application_name' => env('DB_APPLICATION_NAME', 'Laravel')
If you don't specify the app name in the .env file the application name will be taken from /config/database.php file.
I'm looking at the Compass-Sinatra starter file on GitHub. Is there a way to set the output_style for an scss file in Sinatra? Ideally I would like to set the style to :expanded when in development.
I think I'm having trouble understanding how sass(:"stylesheets/#{params[:name]}", Compass.sass_engine_options ) works and where I can set those options.
I found that adding the output_style setting to the compass.config file works for changing the output_style. It can either go in the if defined?(Sinatra) block or in the configuration block at the bottom of the compass.config file.
# compass-sinatra-starter/config/compass.config
if defined?(Sinatra)
# This is the configuration to use when running within sinatra
project_path = Sinatra::Application.root
environment = :development
output_style = :expanded # This is where you can set the output_style
else
# this is the configuration to use when running within the compass command line tool.
css_dir = File.join 'static', 'stylesheets'
relative_assets = true
environment = :production
end
# Or if you wanted to have the output_style set for all environments(?)
# This is common configuration
output_style = :compressed
sass_dir = File.join 'views', 'stylesheets'
images_dir = File.join 'static', 'images'
http_path = "/"
http_images_path = "/images"
http_stylesheets_path = "/stylesheets"
Note: stop/start the server if you change the settings if you don't see the change.
For example, I have a styles.scss file in views/stylesheets/styles.scss then if I go to http://localhost:4567/stylesheets/styles.css I'll get the .scss file compiled in the browser to .css. Changing the output_style, start/stop the server the .css output_style changes. I don't know if using reloader would work, but it might avoid the stop/start?
I found a couple of other good resources.
Andrew Stewart has a blog post and a GitHub template
Originally I was trying to learn about media queries in Sass(scss) with Sinatra and found a great video Ben Schwarz posted, but it doesn't go into the nitty gritty of setting up. It's more about the media query. Ben also has the source on GitHub.
But it seems like AssetPack is the best way to go for serving assets.