I've used profile builder to create an install profile based on one of my sites. I've not used it or created my own profiles in the past, just used off the shelf ones.

Drush make looks to download all of the necessary files but when I try to install the site with the profile it starts configuring everything and gets to about 59 out of 100 and then errors saying

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mysite.rdf_mapping' doesn't exist

Sure enough the base RDF table is missing hence the error but the rdf module is listed as a dependency in the .info file. Is this likely to be a problem with the order modules are being installed in or does anyone have any guidance as to how to look to resolve this?

When the profile was built the checkbox 'Create defaults like standard profile' was checked.

The contents of the info file are

; Packaging information for general3
name = "General3"
description = ""
core = "7.x"
; ----------
; Dependencies
; ----------
; Administration
dependencies[] = admin_views
; Chaos tool suite
dependencies[] = ctools
; Context
dependencies[] = context
dependencies[] = context_ui
; Core
dependencies[] = block
dependencies[] = color
dependencies[] = comment
dependencies[] = contextual
dependencies[] = dashboard
dependencies[] = dblog
dependencies[] = field
dependencies[] = field_sql_storage
dependencies[] = field_ui
dependencies[] = file
dependencies[] = filter
dependencies[] = help
dependencies[] = image
dependencies[] = list
dependencies[] = menu
dependencies[] = node
dependencies[] = number
dependencies[] = options
dependencies[] = path
dependencies[] = rdf
dependencies[] = search
dependencies[] = shortcut
dependencies[] = system
dependencies[] = taxonomy
dependencies[] = text
dependencies[] = toolbar
dependencies[] = update
dependencies[] = user
; Development
dependencies[] = devel
dependencies[] = profiler_builder
dependencies[] = profiler_builder_extras
; Feeds
dependencies[] = feeds
dependencies[] = feeds_tamper
dependencies[] = feeds_tamper_ui
dependencies[] = feeds_ui
; Fields
dependencies[] = addressfield
dependencies[] = addressfield_tokens
dependencies[] = field_group
dependencies[] = field_multiple_limit
dependencies[] = field_validation
dependencies[] = node_reference
dependencies[] = references
dependencies[] = smart_trim
; FlexSlider
dependencies[] = flexslider
dependencies[] = flexslider_views_slideshow
; Mail
dependencies[] = simplenews
dependencies[] = simplenews_realname
; Media
dependencies[] = imagecache_actions
dependencies[] = imagecache_canvasactions
dependencies[] = imce
; Other
dependencies[] = auto_entitylabel
dependencies[] = auto_nodetitle
dependencies[] = block_class
dependencies[] = block_titlelink
dependencies[] = clone
dependencies[] = colorbox
dependencies[] = entity
dependencies[] = entity_token
dependencies[] = field_formatter_settings
dependencies[] = invisimail
dependencies[] = job_scheduler
dependencies[] = libraries
dependencies[] = linked_field
dependencies[] = multiblock
dependencies[] = node_page_admin
dependencies[] = pathauto
dependencies[] = prepopulate
dependencies[] = redirect
dependencies[] = shs
dependencies[] = special_menu_items
dependencies[] = token
dependencies[] = tvi
dependencies[] = weight
; Performance and scalability
dependencies[] = blockcache_alter
; Rules
dependencies[] = rules
dependencies[] = rules_admin
dependencies[] = rules_scheduler
; SEO
dependencies[] = metatag
dependencies[] = metatag_ui
dependencies[] = metatag_views
; Spam control
dependencies[] = captcha
dependencies[] = recaptcha
; Statistics
dependencies[] = googleanalytics
; Theme Tools
dependencies[] = delta
dependencies[] = delta_ui
dependencies[] = omega_tools
; User interface
dependencies[] = imce_wysiwyg
dependencies[] = jquery_update
dependencies[] = superfish
dependencies[] = wysiwyg
; Views
dependencies[] = better_exposed_filters
dependencies[] = views
dependencies[] = views_bulk_operations
dependencies[] = views_slideshow
dependencies[] = views_slideshow_cycle
dependencies[] = views_ui
; Webform
dependencies[] = webform
; XML sitemap
dependencies[] = xmlsitemap
dependencies[] = xmlsitemap_custom
dependencies[] = xmlsitemap_node
dependencies[] = xmlsitemap_taxonomy

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Ollie222’s picture

Issue summary: View changes
Ollie222’s picture

I believe my issue with this is down to me testing php 5.6.0 and there being an issue with mbstring configuration.

https://www.drupal.org/node/2332295

After changing the configuration the install from the profile now looks to have worked.

Ollie222’s picture

Status: Active » Closed (fixed)
GuyPaddock’s picture

kingfisher64’s picture

I'm getting the same with latest version of profile builder 1.2.

The php version is 5.4 not 5.6 for me so I'm not sure #2 is relevant for me.

Being honest I'm not sure if #4 linked solution is fixed as it says failed testing. I'm no dev so unfortunatly can't fix this.

I get the following errors:

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table '98_profiler.rdf_mapping' doesn't exist: SELECT bundle AS bundle, mapping AS mapping FROM {rdf_mapping} rdf_mapping WHERE (type = :db_condition_placeholder_0) AND (bundle IN (:db_condition_placeholder_1)) ; Array ( [:db_condition_placeholder_0] => mailchimp_activity_entity [:db_condition_placeholder_1] => mailchimp_activity_entity ) in _rdf_mapping_load_multiple() (line 213 of modules/rdf/rdf.module).

Notice: Undefined index: field in _fences_theme() (line 30 of modules/fences/fences.admin.inc).

@Ollie222 & GuyPaddock did you manage to install your profile? If so have you learned how to solve this?

Many thanks for your time

btopro’s picture

maybe try having rdf higher in the install profile; also run profiler_builder dev and don't turn on the experimental sub-module unless you know why you are doing so. The issue referenced in 4 isn't a solution and is a core issue which could be manifesting here but not positive.

kingfisher64’s picture

Right thanks btopro for clearing up #4 and taking the time to reply, your help is very much appreciated.

Tried the dev now. Put core at top of install profile. Now getting:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://domain/install.php?profile=restaurant&locale=en&id=1&op=do StatusText: OK ResponseText: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes) in modules/backup_migrate/includes/crud.inc on line 24

@btopro - what should I do now?

Thanks again.

btopro’s picture

sounds like you are on shared hosting perhaps? That's related to memory allowed for PHP not being high enough. any ability to look that up / set that on the server? Altho that's really high to be capping out at 268 megs or whatever that is.

kingfisher64’s picture

I'm on a virtual server with customisable limits but I would have thought 256mb should be enough? It does get to 100% but then the following error is output:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 130968 bytes) in includes/theme.inc on line 76

I turned off variables and it got this far. Not sure what else to try?

Can remove more modules but I do need a vast majority of them.

kingfisher64’s picture

I'm sorry to say that regardless of how much I uninstall I just can't get this to work.

On wampserver the profile page (exclusive flag ticked) just hangs and doesn't proceed beyond that.
On a live server it runs out of memory everytime.
Maybe I've simply got too many modules installed and it's nothing beyond that.

Tried about 20-30 different times.

The relevant bit for this thread is moving the core section of dependencies to the top of the .info file and rdf to the top of that. This error then disappears.

btopro’s picture

"On wampserver the profile page (exclusive flag ticked) just hangs and doesn't proceed beyond that." is the profiler library included / added to the .info file of the profile? did you clean up any todo's / modify the profiler_builder stuff at all? If you have features that install permissions that is the #1 source of things failing from past experience. Maybe see if you can get things to install without all the modules to try and invalidate what's going on because I don't think this is related to profiler_builder (directly at least) from how you describe it.

kingfisher64’s picture

Hi btopro,

Right I've had another 4 or 5 goes today.

Things tried:

checked .make file for todo - there was 1, which is now fixed
edited .info file moving rdf to very top of core section and moved core section to very top of file
uninstalled features so features permissions don't figure
downloaded profile library and installed it in profiles/myprofilename/libraries/profiler
have told it now not to include one .htaccess patch

I now get:

Fatal error: Call to undefined function db_table_exists() in modules/user/user.module on line 4067
Which leads to https://www.drupal.org/node/1093420 and then https://www.drupal.org/node/2412003 #1 patch works but install still won't complete.

Profiler setup

I've been trying installs:

using the latest dev version (+8) and beta2 of profiler library
with and without include profiler selected
with and without variables
with and without create defaults like standard profile
always set to exclusive

The options used in the latest build attempt are in the attached screenshots along with the exact setup error.

Thanks again.

Edit: the output error on one of the screenshots is the error that ollie222 posted in the original post.

btopro’s picture

check into drupal.org/node/1093420

kingfisher64’s picture

yep i've done that btopro. the patch works from there however

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mysite.rdf_mapping' doesn't exist

still keeps appearing. Thought i'd got rid of it by putting it to the top of the .info file. Apparantly not.

kingfisher64’s picture

Priority: Normal » Major
Status: Closed (fixed) » Active
btopro’s picture

Priority: Major » Normal
Status: Active » Closed (won't fix)

This issue was closed, open a new one if you feel there is a new issue. OP had problem and resolution described; this is not an issue with profiler builder, more likely an issue with install profiles in general or a nuance in what you are doing on your build.

kingfisher64’s picture

Okay understood, thanks btopro.