Darren Ethier (nerrad)
Forum Replies Created
-
of course its possible. You just need to make sure the series custom taxonomy registration is modified so that it registers for pages as well. The beauty of opensource is you can go in and customize the code any way you want.
However, there are other things here and there that will need to be modified as well (some custom queries that only search the post type will need to include the page type as well).
hey there! I replied to your comment on OrganizeSeries.com but I’ll reply here as well.
Bulk-edit is something that I’ve considered creating an addon for and it is in the development queue but is not a high priority. Part of the difficulty of adding this feature is thinking through how series parts will be determined. My initial thoughts would be to just order them by post-date when bulk-edit is used. It becomes really complicated if we implement some sort of part chooser in the process.
so orgseries 2.3.5 works fine on multi-site but orgseries 2.3.6 produces the errors you’re getting? hmmm… I’ll take a look at the changelog but off the cuff I can’t think of anything that would be producing your errors. It does sound more like a bug if 2.3.5 works fine.
no, it won’t be done by the weekend. Working on a project with a client right now and it has priority atm. I have had people sponsor development of an addon in the past, if this is something you’d be interested in doing let me know (darren@organizeseries.com)
received notification that you posted a reply here but it isn’t showing up on this page. Anyway, in that notification I noticed that you mentioned something about your site being a multisite install of WordPress. That would probably explain the problems you’re having. Organize Series isn’t compatible with multi-site at the moment. I am developing an addon developed to enable this but it isn’t done yet.
BTW, from the links I followed on Google, it’s highly unlikely this is an Organize Series problem – it looks like its an issue with your server.
That’s a first – never came across that error before (I’ve got Organize Series running on 4 different sites – and try to test fairly throughly). Unfortunately, if I can’t reproduce this I can’t fix it. Here’s the standard troubleshooting tips I give people:
- Try leaving all the plugins you have installed active and switch to the default theme (in this case Twenty Ten). If you don’t have problems you know its a problem with the theme. If you do still have the issue then go to the next step
- Deactivate all your plugins and then just activate Organize Series. If you still have problems then it could be that all the files for Organize Series didn’t get installed properly (try reinstalling it manually). If the problem is eliminated then there is another plugin causing the problem, try activating them one at a time until you find out which one
Also, I noticed that your server is running nginx (not apache). Google your error along with nginx and WordPress and you’ll see that this is reported elsewhere.
That’s the extent of free support I can give you. This is the kind of thing where the paid support option I provide will return value.
If I get a chance I’ll take a look at what is happening. For what it’s worth, Organize Series just utilizes the WordPress uploader for uploading images. There is probably something that Amazon S3 is hooking into with the WordPress uploader that isn’t firing off when Organize Series is using the uploader.
I visited your site (http://www.evangelism.org/series)and it definitely is an error with your theme as output on the page. All the series information is displaying.
As for what happened with your original error it looked like the permalinks just hadn’t been regenerated yet. Glad that is fixed for you.
Short answer. Yes, with the [series-toc] shortcode in the Shortcode addon you can choose to sort asc, or desc.
The /series/chroma-photography page is an archive page and will inherit whatever settings you have for your blog. If you’re blog is set to show full-length articles then the series archive pages will show that.
If you want to just show excerpts you could do that by modifying the WordPress loop in a file named, “taxonomy-series.php” and place that file in your theme directory.
Hi Alessia,
I visited your site, unfortunately I’m unable to duplicate this problem so I can’t yet determine if this is something I can fix (or that Organize Series is directly the cause)
Some questions:
- What version of Organize Series are you currently running and what version did you upgrade from?
- What version of PHP is running on your server?
- What version of WordPress are you running?
In looking over your site and the other series it appears like you’ve upgraded from an earlier version and the upgrade didn’t quite work as it should have.
Forum: Plugins
In reply to: Organize series grouping PHP warningJan, I’m just writing a response to your initial contact to me right now. Very sorry you are experiencing the problems, in my testing I haven’t experienced that but I definitely can see it being a problem. If you could help me out by indicating:
1. What WordPress version are you using?
2. What version of Organize Series do you have installed?
3. What PHP version is installed on your server?
4. Do you have any other plugins installed that manipulate taxonomies (i.e. categories, tags etc.), if so, what do you have installed?Thanks!
Forum: Plugins
In reply to: [Plugin: Organize Series] Breaks Wp-AdminCan you try it with Facebook Comments disabled and just Organize Series? I’d be interested in knowing if things still “break” for you in that scenario. It may also indicate that there is another plugin running on your site that is not only conflicting with Organize Series but also with Facebook Comments.
Forum: Plugins
In reply to: [Plugin: Organize Series] Breaks Wp-AdminOrganize Series 2.3.3 works fine on all the websites I manage that use it (over 4) and I haven’t experienced any of the symptoms you’ve reported.
what version of PHP is running on your server? Organize Series requires PHP 5.2+
If you have the correct PHP version running then it is possible there is a conflict with another plugin.