I would have checked this out sooner, but the day you posted version 1.3 is the day I left for a two week vacation. I’m happy to see this version sitting here now that I’m back!
I just posted a question in another thread about the ‘www’ issue, mainly because of this module: Why does Control Panel redirect drop the ‘www’ if trailing slash is missing in URL?
This module is really the only way I can get the site I’m developing to work correctly, so anything I can do to get it working for everyone who will be updating the site is great.
Just a note that the extension in version 1.3 still reads “1.2”
I’m also wondering why it might be that Selected Items is only working for me when the ‘www’ is in the URL - but an extension like Mark Huot’s “Live Search”, which also uses AJAX, works in the CP whether the ‘www’ is in the URL or not. Is there some small tweak that could be made to allow Selected Items to work in either case?
I just want to note that should dates (2008/02/25/) be added to the url segments on a page that has the selected items weblog tag in it – it throws php error messages at the top of the page.
Notice: Undefined index: 191 in /websitepath/system/extensions/ext.selected_items.php on line 135
It would be great if the errors can be surpressed.
Great Module Andrew!
What would really complement this would be an extension that adds a custom field type allowing you to choose a “Selected Items” collection from a list. This would allow you to associate the list with any entry, rather that with in templates only…
I managed to get this working to an extent using a text field that holds the Selected Items name, and embedding a “dislay selected list” sub-template.
I don’t have any experience creating extensions though… Anyone? I’d be happy to test it out 😊
Andrew - I just noticed a ‘bug’ with this module when working with EllisLab’s Multiple Site Manager.
I just tried it out using two sites and my list of selected items appear for the default site, not the other (no lists appear). As far as I can tell from the docs Modules are supposed to be common across all sites. Other modules installed behave in this way.
I’ll try to find something specific in code to be more specific, though I’m not great with writing modules/extensions etc.
Thanks for the note. I started to add MSM support to the module - I can’t remember how far I had got to be honest.
I think I was setting it up so that selections created on one site did not appear on other sites. I judged this to be the desired behaviour, but are you saying that you would expect selections to appear globally across all sites?
My mistake - after looking through the module, it’s clear you’ve specifically created this to have different collections for different site id’s.
I guess I’m using it in a different way. I might suggest making that a configurable setting for the module.
Thanks again for a great module!
Just a note that the extension in version 1.3 still reads “1.2” I’m also wondering why it might be that Selected Items is only working for me when the ‘www’ is in the URL - but an extension like Mark Huot’s “Live Search”, which also uses AJAX, works in the CP whether the ‘www’ is in the URL or not. Is there some small tweak that could be made to allow Selected Items to work in either case?
To solve this issue I removed the javascript from the mcp.selecteditems.php file and referenced “ajax.js” and “selected.js” the same way they are back in V 1.1.
To avoid multiple version of the module floating around, I’ve removed all the downloads from this thread and set up a central page - Selected Items - that will always have the most recent version.
Andrew
Thanks for this excellent module. I am encountering an error, however, when updating a selection or creating a new one. I receive the following message: “An appropriate representation of the requested resource /ee/sys/index.php could not be found on this server.”
I see some earlier conversation about server path issues. I am running 1.6.2 and using Firefox 3.0.
Thanks for any help.
Hi to everyone who’s been active on this thread. This module/extension/plugin is brilliant, thanks Andrew - a donation will be coming your way shortly!
I’d like to add comments about two different points, first one in response to Jesse McCarthy’s post, which helped me figure out the reason why my client was encountering a problem with the module (thanks Jesse!).
My client was suddenly unable to see the left hand column of selected items - the last time they logged in it had been fine. I was able to see them logged in as super admin. They got this error message:
Line: 1884 Char: 5 Error: Access is denied
Anyway, it was Jesse’s comment below:
* The JavaScript file doesn’t load because I’m Masking Access to the Control Panel. That results in a control panel URL like http://www.example.com/admin.php. The Selected Items control panel page uses the document relative URL “modules/selecteditems/selecteditems.js” to link to the script, which ends up pointing to http://www.example.com/modules/selecteditems/selecteditems.js instead of http://www.example.com/system/modules/selecteditems/selecteditems.js (where “system” could be another name chosen when installing EE).
which pointed me to the problem. Before we went live the client was using a development URL, and they did not switch to using the new URL for the control panel when we went live with the website. So really I’m just confirming that the module does not work correctly unless the URL is the same as that entered into the General Configuration of the Admin area (as is stated elsewhere in this thread).
To make sure your administrator can use the “Selected Items” module, make sure that they have the right privileges first, E.g.
Here: Admin › Members and Groups › Member Groups › Edit Member Group › Administrator
Control Panel Area Access > Can access MODULES page [yes] Module Access Privileges > Can access module: Selecteditems [yes]
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.