I am trying to start a Drupal 7 website. I was provided with a folder containing a Drupal installation, and was to move it to a server with a database supposedly for that installation.
Upon me doing so, Drupal gave me several errors regarding missing modules. After manually installing most of the missing modules, I am left with a single error, which is
User warning: The following module is missing from the file system: post_articles. For information about how to fix this, see the documentation page.
I am unable to find the post_articles module on the Drupal website or anywhere else, and am at loss how to proceed.
It's not a contrib module so you cannot get it from drupal forge, otherwise to unlock your situation you can disable module by query into your database :
UPDATE system SET status=0 WHERE name='post_articles';
But it can be a dependency of another module so be careful when you're disabling module with this way.
Related
I would like to ask you if someone has similar problem. I am using Sitecore.NET 7.2 (rev. 151021) with Solr. I need to add some items from prod to my local sitecore instance. When I create package and tried to install specific content I get exception null reference exception. It doesnt depend on the content. I tried to used package designer with varios content and always I get this exception.
As the comments indicate: Make sure that all of the supporting items that each item in the package require are in place in the destination before trying to install them through a package.
Normally, separate packages are created for Templates, Layouts and Content and installed in that order to avoid missing dependencies.
You can also look into disabling Index builds during package installation. I have a module out there that does this:
https://marketplace.sitecore.net/en/Modules/Detailed_Package_Installer.aspx
Is it possible to set the module category in a DNN manifest file so a package containing lots of related modules can be categorised? It doesn't have to add the the taxonomy, an existing entry is fine.
The DNN Wiki seems to suggest not?
This is not possible currently with DNN. You can only set the Category by editing the module via the extensions page AFTER installing a module.
I am getting dotnet nuke error whenver i try to add a module on my page. It works well on my local system but gives me dotnet nuke error on the server. Any help will be appreciated.
Are you running any custom URL providers, such as Ifinity's URLMaster? If so, be sure to upgrade to the latest release.
If not, what specifically is the error you are receiving?
Also check your \Portals_default\Logs\ folder for any logs that might give you a clue about the error
I'm developing a DotNetNuke Module using the nonIIS method of module development. Is there any way to include a 3rd-party assembly in your module (when setting it up for deployment)?
I thought about adding it as a reference to the dotnetnuke_nonIIS website project as a whole, but that doesn't seem right considering it's a dependency of the module.
Whatever your local development environment may look like, you will most likely want to be able to deploy the module to a DNN site on its own.
To do that, you can create an installable module zip package - which consists of all of your module assets and a manifest file describing them so that DNN may process them and perform the appropriate actions (run scripts, deploy assemblies to the bin) upon installation.
Check out the DNN wiki for more information about packaging.
I am trying to install a module in a DNN project residing on Godaddy.
I am getting an error installing the module
I know the error I am getting in DNN is coz of permissions.
I thought giving write permissions to the App_Data and DesktopModules folder will resolve the error, but it doesn't, is there any other folder I have to give write permission to
BTW, I am trying to install the already existing "Feedback" module in DNN
Okay the Feedback module and most modules that are installed as PA's have binary/compiled files for the data provider and much of the actual code for the controls. First thing I would check is that the 'bin' folder has write permissions as well as 'app_code' and 'desktopmodules'