Converting to Drupal

Dear all,

I’m working for an international organization and we are planning to move our website on the Drupal 7. At the moment, we have a custom CMS that contains numerous articles, pages and large collection of pdf documents (around 60.000) stored in a database. For pdf documents we are considering development of a custom module that would retrieve data from the old database as the functionality of this part of CMS and website is quite specific, while the content of our articles and pages (without comments) needs to be migrated to the Drupal database.

I'll start by staring that I am not really a developer, but I play one on TV. I'm mostly just very techy with a bit of ASP, PHP, and JavaScript knowledge.

My employer has two primary CMSs currently, one that is completely custom coded and the other is on SharePoint 2007.

We have a plan to move the SharePoint site to 2010 that will likely launch at some point this year, but has a chance of stalling completely. As the potential to stall might imply, decelopment of the 2010 site isn't goong well, and management os looking to explore other options. The end goal was to after launching the 2010 site we plan to manually migrate all of the content from the custom coded site into a separate instance on the SharePoint site. The reason being that while both sites have different audiences, there may be some information that is shared, and we would like to only create the content once. The next steps would then be to possibly have additional instances that would allow content to be shared with our public site (Adobe CQ5) and our employee information intranet site (DotNetNuke).

Hi, I can not understand how to use migrate_extras and for example how to use geofield migrate extra support.

I have create a Migration class that work. In my "source" I have 2 "fields" called latitudine and longitudine. I have follow the instruction that I have found in geofiled.inc:

$geo_arguments = array(
      'lat' => array('source_field' => 'latitudine'),
      'lon' => array('source_field' => 'longitudine'),
    );
    // The geometry type should be passed in as the primary value.
    $this->addFieldMapping('field_coordinate', 'Point')
         ->arguments($geo_arguments);
    // Since the excerpt is mapped via an argument, add a null mapping so it's
   // not flagged as unmapped.
    $this->addFieldMapping(NULL, 'latitudine');
    $this->addFieldMapping(NULL, 'longitudine');

But my "test node" is created (via migrate) without "geofileld" field (field_coordinate). But if I comment the lines above and insert this function:

public function prepare($node, stdClass $current_row) {
$node->field_coordinate = array(LANGUAGE_NONE => array(0 => array('geom' => 'POINT ('.$current_row->longitudine." ".$current_row->latitudine.')',
'geo_type' => 'point',
'lat' => $current_row->latitudine,
'lon' => $current_row->longitudine,

Greeting:

I am looking for a near to out of the box solution to replace an existing MS Access database that is nearly 20 years old. This database is used to track articles for a journal through all stages of approval to the point of rejection or publication. We would like to move this to an online database with added functionality

Current database accepts entries for
Biographical information about the article including name of author, title, genre, searchable fields etc
Who is reviewing the article
approval status
etc

System can also generate letters of rejection, approval, review, etc

need to recreate this functionality on launch

desired functionality
submitter to be able to self create their own account/profile including details on their background and other biographical information
submitter able to self submit articles to be published in PDF or other format which is stored and cataloged
articles are able to be submitted to reviewers electronically via the CMS for review, comment and approval
Reviewed articles can be rejected back to the submitter for revew/revision and resubmission
ability to recommit articles for review
ability to generate electronic approval/rejection notifications
document repository to store documents for however long desired

Greetings to the community!

Hello everyone:

I am new to drupal but have read the drupal ebook and watched about 5 hours of videos on getting started with drupal. I did set up a test folder on my godaddy server and everything was ok until I installed the subdomain module to figure out how i was going to re design my site

the site is not huge but has enough subdomains and subfolders that this is going to be a little tricky.

I have to make sure the site has all the same exact URLs since I have been link building to it for years

Here are some basic examples of what I am dealing with

maindomain.com

Then I have 8 subdomains

1.maindomain.com
2.maindomain.com
3.maindomain.com
4.maindomain.com
5.maindomain.com
6.maindomain.com
7.maindomain.com
8.maindomain.com

Then within each subdomain I have between 1 and 5 holders

2.maindomain.com/folder1
2.maindomain.com/folder2

Then in some cases I have a second folder inside the first folder

2.maindomain.com/folder1/folder2

I was hoping to do one installation into the root folder on my godaddy server and build it from there but I am not sure if it going to be possible since I don't know much coding and need to get it up quickly

also some of the subdomains will have its own blog.