So our developer has upgraded the back-end from 7 > 7.4, but in doing so this causes all sorts of issues w/ trailing slashes that weren't a problem in 7.0. Anyone have any idea why this breaks Drupal? ie: mysite.com/user worked fine in 7.0, but doesn't resolve in 7.4 to the admin page... We've played around with .htaccess, but that inverts the problems: on urls that worked, they break & vice-versa... Server environment has both 7.0 version & 7.4 version running in separate vhosts, so they're isolated. And I know I'm not the first person to run 7.4 under SuSu11...
Hi all,
Im brand new to this so please bare with me, Im a newb.
Im trying to use flot in drupal 7.4, but I havent been able to locate a module.
can I use the module from version 6.x or will that cause problems?
I have a domain name setup through GoDaddy (call it othersite.com)
I also have another GoDaddy domain (mainsite.com) that also has a GD hosting account. That domain has a subdomain setup with a Drupal install (call it sub.mainsite.com but setup at /sites/sub.mainsite.com in the directory)
I want othersite.com to point to sub.mainsite.com but I'm a little confused as to how to go about setting that up. I have othersite.com pointed to the IP address of mainsite.com, but I'm not sure how to specify, specifically, that I want it to go to sub.mainsite.com.
I have created a custom module which successfully displays most simple data from an external MySQL database in a View. I have a DATETIME field in the external MySQL table and I'm currently getting the following warning:
Warning: date_timezone_set() expects parameter 1 to be DateTime, boolean given in format_date() (line 1909 of ...site/includes/common.inc). Warning: date_format() expects parameter 1 to be DateTime, boolean given in format_date() (line 1919 of ...site/includes/common.inc).
If I change the handler in custom module_views_data from views_handler_field_date to views_handler_field the field appears fine in the View without errors.
Does Drupal 7 Date support DATETIME in an external MySQL DB? Some code comments suggests it is looking for a TIMESTAMP....the error message at 1909 in the code fails while trying to convert from TIMESTAMP to DATETIME... somehow failing near the code:
// Create a DateTime object from the timestamp.
$date_time = date_create('@' . $timestamp);