I have an existing site running BlogEngine.NET 1.5 and will be upgrading it to the new 1.6 release. I have been asked to integrate Disqus for comments. I have not found any other questions on Disqus and BlogEngine.NET.
I have found some specific instructions here:
http://www.hamishgraham.net/post/Enabling-Disqus-Comments-in-BlogEngineNET.aspx
It explains how to add Disqus to a specific BE.NET theme. But I have existing blog posts and comments. How will these 2 systems work side-by-side? Is there a way to somehow make Disqus work well with the existing comments?
Links:
http://www.dotnetblogengine.net/
http://disqus.com/
Check out the Blogengine.net 1.6.1 release. Disqus is now integrated into the admin area to make it really easy to set up.
Here is a link to the post detailing the install instructions:
http://www.dotnetblogengine.net/post/BlogEngine-161-Update.aspx
Only the web release version is available for 1.6.1 though. I would suggest downloading the source for version 1.6.1 and compiling yourself if you need to customize your build. Here is the link: http://blogengine.codeplex.com/SourceControl/changeset/changes/9f0455258305
Disqus will be integrated with BE.NET in the update pack which will be released in April. You might want to hold on just a little bit and then get it working by simply updating to latest.
You should be able to migrate your comments to/from Disqus with their migration tool (http://import.disqus.net/).
Related
I have a serious problem.my website, written in WordPress with theme = Envo eCommerce 1.1.1, no longer works although I have not made any changes. In July the website has undergone automatic updates to version 6.0.1.
Since that time the block editor (classic paragraph) hasn't worked anymore. Unknown error.
The strange thing is that I have two websites structured in the same way. One works and the other does not.
Is there anyone who has encountered the same problem and solved it?
In that case I would like to ask him for help.
I thank those who are reading me in the hope of finding a solution.
Good job everyone.
RenatoDerik
Is the version 5 of Plone finally having an official multilingual solution that work? I did try Plone 4 but no multilingual solution was official or was working properly. I hope Plone 5 fix the problem.
plone.app.multilingual is a standard part of Plone 5. After installing Plone 5, activate it via the "add ons" control panel of site setup. Then use the "Languages" control panel to set available languages and translation parameters.
For earlier versions of Plone, install Products.LinguaPlone via the usual add-on package mechanisms. While LinguaPlone does not ship with Plone 4.x, it is a well-supported content-translation mechanism and it does work (though plone.app.multilingual is much better). Translation of Plone's user interface does not require LinguaPlone; it is meant to support content translation.
Both solutions also support adding translation support for custom content types.
We've recently had several hacks on our one server. We've been advised to upgrade all scripts. The problem is, the Drupal installations. Upgrading these are a massive task. I would like to know, out of fellow Drupal users, in your experience, how unsafe is it to remain on a say version 6.10 as apposed to upgrading 6.28 (the latest)? Is there a point at which you can say: this is really too old now and an upgrade is absolutely necessary?
I'm not too worried about the modules, my concern is the Core Drupal installation. Does it ever become a security risk, or can you stay on the older versions?
"Upgrading these are a massive task"
Not necessarily! I find using git a pretty safe way to deal with such upgrades.
My basic workflow is usually to:
- create a repository with the current Drupal version.
- download the latest core version
- rsync the current version with the latest core version
- update the repository
As expected, I do all of the above on my local version, after checking that everything is working fine. I update the remote repository, then update the actual live site from git.
If you're not familiar with git, basic tutorials are easy to find online. The idea here is not to explain the process in details, rather to send you in the right direction. You will find that it's a pretty flexible workflow, a great way to update modules and generally any type of code.
I'm having some problem with a custom made plugin since upgrading to the newest wordpress version. I've made downgrades before, so that's not the problem. This, however, is a multi site and I'm uncertain if it makes a difference when making the downgrade? Is it the same or should it be avoided?
And, yes, I know I should probably change the plugin, but it is vital for the site!
Not much of a conclusive answer really, but I am fairly certain I have successfully downgraded downgraded a WPMU site in the past (before it was renamed Network Site). Just load /wp-admin/upgrade.php as you would normally do. I would strongly recommend you do the downgrade on a development system before performing it on you production site.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
A WordPress plugin that has always worked OK in the past suddenly isn’t working, why do this type of error in wordpress?
Make sure that you’ve downloaded the latest version of the plugin. New releases of plugins add features, but they also often fix bugs, including the one you might be having.
To check for new versions of your plugins, just click Administration and Plugin. WordPress should list all of your plugins, along with notifications of any that have upgrades available. Click Upgrade Automatically, and you’ll have the latest version. (In fact, checking for the latest versions of all of your plugins is something you probably should do on a regular basis, perhaps two to four times per year.)
If that doesn’t work, you have a few other options. You can try reinstalling the plugin from scratch; perhaps the plugin software became corrupted. Try to remember if you made any other software changes or installed other plugins between the time the problematic plugin was working correctly and the time that it failed.
You could have an incompatibility issue between the malfunctioning plugin and the software changes you made. See if the author of the plugin has a blog where you can report your problem. It’s possible others are having the same issue, and the plugin author will create a fix or knows a workaround.
Occasionally, if you upgrade your version of WordPress, you could end up with multiple plugins that stop working correctly. You’ll just have to deactivate the malfunctioning plugins until the author comes up with a new release that will be compatible with the new version of WordPress.
if you want more details click here. Link
You've probably upgraded your Wordpress version and the plugin is no longer compatible. Another possibility is that you've installed a conflicting plugin or changed some settings. You could also have used the plugin incorrectly inadvertently.
It would help if you explained what plugin you're using, what error you're getting, and what you're trying to do with it.
If a wordpress plugin stops working it could be for a number of reasons:
It was relying on a web service which no longer exists/returns and is not handling this case gracefully
Someone has upgraded to the latest version which no longer plays nice with the version of WP you're running or the version of PHP you have installed.
Another plugin that you have installed is now conflicting with the plugin.
Have you enabled wp-debug in the wp-config file?
if you plugin stop working first question you have to ask yourself is:
1.- Did I install another plugin so it's having conflict with jquery (for example)
2.- Did I recently upgraded WordPress. (perhaps that plugin doesn't work with the new version)
and then you could have more answers depending on which plugin is.