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.I installed OpenChurch, and everything was working well. As I attempted to add a couple of additional modules, I suddenly received a message that the module media_wysiwyg was missing, and the database update would not continue. I backed up, and checked my modules, and sure enough, there was no media_wysiwyg module listed. I went to www.drupal.org/projects/media_wysiwyg and... nothing. No such page. From what I'm gathering, it appears to be somehow related to Panopoly. If I attempt to activate an inactive module that is already installed, I get a prompt,
"The media_wysiwyg module is missing, so the following module will be disabled: panopoly_wysiwyg.
Would you like to continue with the above?"
I was notified that I had modules which needed to be updated, so I went through the update process, which went fine, until Drupal attempted to update the databases, at which time I was given an "unresolved dependancy" error (see attached screenshot). I seem to be stuck, unable to complete any updates, or add any modules, until I get this resolved.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | LSDA-OC-Updates.png | 158.55 KB | LaconiaSDA |
| #7 | GUI-Not.png | 31.09 KB | LaconiaSDA |
| #7 | GUI-Working.png | 182.31 KB | LaconiaSDA |
| drupal_error.png | 64.04 KB | LaconiaSDA |
Comments
Comment #1
LaconiaSDA CreditAttribution: LaconiaSDA commentedI need some help on resolving this problem. Development of this site is basically dead in the water, until I can resolve this issue.
Comment #2
drupalninja99 CreditAttribution: drupalninja99 commentedHmm that is strange, that must be a new dependency?
Comment #3
drupalninja99 CreditAttribution: drupalninja99 commentedOne thing I would do is restore your openchurch profiles folder to its original state by re-downloading it. A lot of panopoly modules are patched, so if you downloaded an unpatched version it probably broke it.
Comment #4
drupalninja99 CreditAttribution: drupalninja99 commentedI am pretty sure this has to do with probably an upgrade to maybe a patched panopoly module.
Comment #5
drupalninja99 CreditAttribution: drupalninja99 commentedI updated the 2x dev version just now so if you download the latest you should be mostly up to date.
Comment #6
LaconiaSDA CreditAttribution: LaconiaSDA commentedOK. Just to clarify, how do I do that, without wiping out my existing site? Would it be just like applying a drupal core update, just don't copy over the SITES folder, or how should I do it? There are a lot of pieces in this that are rather unfamiliar to me, so I want to be sure to ask questions, rather than lose work.
Comment #7
LaconiaSDA CreditAttribution: LaconiaSDA commentedOK, I misunderstood your statement about downloading the latest; thought you meant to re-install something. I got the latest round of updates, and the above issue is fixed, but now we have a new quirk. Any time that I go into any Edit field for any content, whether it is attempting to create new content, or edit existing, it appears as though it loses CSS. (See attachments). With this as it is, I'm unable to edit or create any content at all. Is this a bug that needs fixed, or is this a problem on my end? Whichever the case, I hope we can get it resolved quickly.
Comment #8
LaconiaSDA CreditAttribution: LaconiaSDA commentedThe problem would appear to be somewhere in the recent updates of Panopoly. I was setting up another site (not OpenChurch) that uses Panopoly. When I ran the updates routine, upgrading from the installed version of Panopoly, I encountered the same issue. I need to get this resolved, as I now have TWO sites that are dead in the water. Hoping, since we've found the problem, that we can find a quick resolution.
Comment #9
LaconiaSDA CreditAttribution: LaconiaSDA commentedOK. I need help.
I know HTML and CSS, and I have a basic grasp of Drupal. I have set up Drupal Core from scratch, I'm comfortable adding modules, themes, and such. But I'll admit, "Distributions" are something new to me. I was of the understanding that a distribution was basically a "turnkey" setup, where someone had taken Drupal Core, and added certain modules, a theme and such, so that the general setup was done for you. But from there, as I understood it, maintenance was no different from Drupal Core. I'm starting to gather that this isn't the case. Dsnopek has me questioning if it was my error that caused the problem I'm experiencing. I have done a fresh install of Open Church. As soon as the new install is set up, I'm given this notice that there are updates, and given a big list of modules and such that need to be updated (see attachment). After my recent experience, I'm waiting to do any kind of updates until I'm told what I should, and should not update through this screen.
The updates it lists are:
Apps
Breakpoints
Calendar
Colorbox
Context
Features
File entity (fieldable files)
JQuery update
Link
Media
Media: Vimeo
Media: YouTube
Metatag
OpenChurch
Panels breadcrumbs
Panopoly Admin
Panopoly Core
Panopoly Images
Panopoly Magic
Panopoly Pages
Panopoly Theme
Panopoly Users
Panopoly Widgets
Panopoly WYSIWIG
ShareThis
Universally Unique IDentifier
Webform
OpenChurch Theme
Responsive Bartik D7
And then Drupal Core requiring a manual upgrade from 7.31 to 7.32.
Someone please advise which of these I should check to allow to automatically update at this point. Previously, when I updated Panopoly this way, is when my original issue started.
Also, I have the site hosted on Bluehost, but I am fairly new to this host, and I will admit, I'm not sure where to find the PHP and Webserver logs.
Comment #10
drupalninja99 CreditAttribution: drupalninja99 commentedI am going to update all modules this weekend.
Comment #11
drupalninja99 CreditAttribution: drupalninja99 commentedUpdated core/panopoly in 2x dev
Comment #13
drupalninja99 CreditAttribution: drupalninja99 commentedComment #14
LaconiaSDA CreditAttribution: LaconiaSDA commentedOK. When I work with just Drupal Core, and add my own modules, when I go to upgrade from, say 7.33 to 7.34, I download the new core, open it locally, I FTP in to my server with FileZilla, I select everything in the local (New version) folder. I then UN-Select the Sites folder, robots.txt, .htaccess and .gitignore, I put the site into maintenance mode, and I FTP everything else over, telling FileZilla to overwrite existing files with the new. Once everything has been transferred, I run update.php, and once it is complete, I check my modules, to make sure it is showing the new version for the core, I take the site out of maintenance mode, and.... we're updated.
Now Distributions are new to me, as I've said. I see there is a beta version here on drupal.org to download. My question is, to update a DISTRIBUTION, would I use the same process as with the core? Are there other steps, or anything?
Thank you.
Comment #15
LaconiaSDA CreditAttribution: LaconiaSDA commentedOK, I just looked on the updates list, and I see "OpenChurch" updating from 7.x-2.0-beta1 to 7.x-2.1-beta1. I presume that I don't need to fool with the steps above, I can just let the updater do its thing? Yes, I'm being a little gun-shy here, probably asking what appear to be some silly questions; I jumped into updates before, and had problems, so I'm wanting to be 150% sure I'm doing things right this time. (I REALLY don't want to have to re-build the whole site AGAIN!).
Thank you.
Comment #16
drupalninja99 CreditAttribution: drupalninja99 commentedYou are doing things the same way you do core. Replace everything but you sites folder and run update.php.