etling

So, is the solution to the original question to add domain names to the whitelist in config.php, like below? /** * Installer: HTTP Hosts Whitelist * */ $config->httpHosts = array('localhost','example.com','www.example.com');

I'm not sure how to even phrase this question, I think I need to learn more specific vocabulary to even ask it. But here goes: With a Processwire site, how does one deal with synchronizing data between a local development database and a live production database? Specifically, the following scenario. Let's say I'm developing a site for a small business client: I develop the site locally, and eventually deploy it to a server The client starts using the CMS, and entering data which is saved in the production database The client requests a new feature -- let's say it requires adding a few fields to an existing template I add the fields to the template on my local development machine Now how do I get those changes to the live site, without overwriting the data the client has already entered? The way I am currently handling this is as follows: I ask the client to stay out of the admin area and stop making changes I dump the production database, and import it to the local dev database I make the changes to the fields / templates I dump the dev database, and import it to the production database Is there a better, more efficient way? Are there specific database tables that define the "idea" of fields and templates, but not their content? In the Rails world, this sort of task would be a "rake db:migrate". One solution, I guess, would just be to connect my local dev site to the live production database once a site is live. But I prefer to be able to work offline if needed, and sometimes I'm dealing with shared hosting services that have limited or unreliable external database access. Forgive me if this is covered elsewhere, or already has a well-documented and obvious solution. I would love to hear any thoughts or suggestions.

Ahem. Fixed this problem, in my attempts to do "admin themes as modules" I had removed the wire/templates-admin/ directory by mistake. So, there were javascripts/assets/stuff missing that made that field collapsible. I'd delete this post, but maybe it can help someone else in the future should they experience this.

Hello. I'm starting a new project on Processwire 2.4. I'm experiencing some funky behavior, as follows: 1. I add a new custom field and save it. 2. Try to edit the field, and the "description" attribute is grayed out, and I can't add a description. I'm experiencing it with all field types. Has anyone else experienced this? I did some futzing around with the admin theme, trying to use the new "themes as modules" method, and I'm wondering if I screwed something up or if it is an actual bug in 2.4 A screenshot is below. This is after saving the field, and opening it up to edit. Thanks for any help, Will

Just throwing this in this forum in case anyone is getting 500 errors on GoDaddy with Linux hosting package. As of 12/9/2013, I was getting a 500 error on every page with the default .htaccess. I went through line by line and found that commenting out the HTTP_MOD_REWRITE variable fixed the problem: #SetEnv HTTP_MOD_REWRITE On I don't know the real cause of the problem, but after four+ hours of trying different solutions, this is what worked for me. My full htaccess file now looks like this (stripped out comments for brevity): Options -Indexes Options -Multiviews Options +FollowSymLinks ErrorDocument 404 /index.php <Files favicon.ico> ErrorDocument 404 "The requested file favicon.ico was not found. </Files> <Files robots.txt> ErrorDocument 404 "The requested file robots.txt was not found. </Files> <FilesMatch "\.(inc|info|module|sh|sql)$|^(\..*)$"> Order allow,deny </FilesMatch> <IfModule mod_php5.c> php_flag magic_quotes_gpc off php_flag magic_quotes_sybase off php_flag register_globals off </IfModule> DirectoryIndex index.php index.html index.htm <IfModule mod_rewrite.c> RewriteEngine On AddDefaultCharset UTF-8 #SetEnv HTTP_MOD_REWRITE On RewriteBase /dev/ RewriteRule "(^|/)\." - [F] RewriteCond %{REQUEST_URI} (^|/)\.htaccess$ [NC,OR] RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets/(cache|logs|backups|sessions|config|install|tmp)($|/.*$) [OR] RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/install($|/.*$) [OR] RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets.*/-.+/.* [OR] RewriteCond %{REQUEST_URI} (^|/)(wire|site|site-[^/]+)/(config|index\.config|config-dev)\.php$ [OR] RewriteCond %{REQUEST_URI} (^|/)(wire|site|site-[^/]+)/templates-admin($|/|/.*\.(php|html?|tpl|inc))$ [OR] RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/templates($|/|/.*\.(php|html?|tpl|inc))$ [OR] RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets($|/|/.*\.php)$ [OR] RewriteCond %{REQUEST_URI} (^|/)wire/(core|modules)/.*\.(php|inc|tpl|module)$ [OR] RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/modules/.*\.(php|inc|tpl|module)$ [OR] RewriteCond %{REQUEST_URI} (^|/)(COPYRIGHT|INSTALL|README|htaccess)\.(txt|md)$ [OR] RewriteCond %{REQUEST_URI} (^|/)site-default/ RewriteRule ^.*$ - [F,L] RewriteCond %{REQUEST_URI} "^/~?[-_.a-zA-Z0-9/]*$" RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !(favicon\.ico|robots\.txt) RewriteRule ^(.*)$ index.php?it=$1 [L,QSA] </IfModule>