Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
I got following warning when importing an panel from another localhost testsite on the content-tab:
warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home:/var/lib/php/session:/tmp:/var/www/html:/usr/share/horde:/usr/share/pear) in /home/public_html/includes/theme.inc on line 611.
The content tab is not shown correctly.
greetings,
Martijn
Comments
Comment #1
merlinofchaos CreditAttribution: merlinofchaos commentedCan you cut & paste the panel you're important? (Feel free to cut relevant strings if you need privacy). I don't have any idea why a panel import would even be looking at files like this.
Comment #2
Summit CreditAttribution: Summit commentedHi,
here is the panel I tried to import:
Thanks for looking into this!
greetings,
Martijn
Comment #3
merlinofchaos CreditAttribution: merlinofchaos commentedIt looks like the error you're seeing is somehow related to theme('image') -- which is quite odd and I don't understand why it might be connected.
This export is too old for me to import now, it seems; or at least, it claims it can't get an import.
It may be due to the PHP code -- you have some bare words in there that are bad form and not guaranteed to work everywhere. It's vaguely possible they might be interfering with the parser somehow, though that seems unlikely. But I have no other theories about what is going on here.
Comment #4
merlinofchaos CreditAttribution: merlinofchaos commentedComment #5
Summit CreditAttribution: Summit commentedHi Earl,
I will look into this again.
It is not a big issue, because it is only with import-export.
With the then newest .dev I will try the export-import again and report you back the result.
I think it is indeed php-code which is the problem.
Great Yearending!
Greetings,
Martijn
Comment #6
sunMarking as fixed for now.
Comment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #8
mstrelan CreditAttribution: mstrelan commentedThis issue still exists in 6.x-3.x when you have a flexible layout with a machine name longer than 24 characters.
The field panels_layout.name is a varchar(255) yet panels_display.layout is a varchar(32). The latter needs enough room to prefix the layout name with a word like "flexible". Therefore the former needs to be restricted to 32 minus max_length_of_prefix or perhaps the latter could just reference the layout id rather than the layout name?
I am marking this as critical because it can corrupt existing pages. After experiencing this issue I deleted my page and tried to recreate it, but then ran in to duplicate entry issues because some of the old stuff wasn't removed, most likely because it was looking for the truncated machine name.
Comment #9
esmerel CreditAttribution: esmerel commentedPlease open a new issue - this one has been closed for over two years. These aren't even the same pieces of software anymore.
Comment #10
esmerel CreditAttribution: esmerel commentedComment #11
mstrelan CreditAttribution: mstrelan commentedIf you're searching for this issue because you get it in Drupal 6 see #956394: Database column not large enough making it impossible to assign a layout to a panels page