Page 1 of 1
phplayers / start_element
Posted: Mon Jan 24, 2005 2:45 pm
by user667
Hi,
I've got a small problem with the start_element tag for the phplayers menu.
My content structure currently is:
1 (content_id=1)
1.1 (content_id=13)
1.1.1 (content_id=14)
2 (content_id=12)
2.1 (content_id=15)
3 (content_id=7)
4 (content_id=10)
5 (content_id=11)
The problem is: no matter what I set the start_element parameter to, the menu is always emtpy
I tried the content number (1.1 or 2.1) as well as the content_id's - with the same effect.
Since the feature seems to be quite simple to use, I'm sure I'm making some very fundamental mistake
Any help would be appreciated.
phplayers / start_element
Posted: Mon Jan 24, 2005 3:11 pm
by Ted
Sounds like a definite bug. I'll take a look at it tonight and see if I can track is down.
phplayers / start_element
Posted: Mon Jan 24, 2005 4:39 pm
by Greg
I noticed when I upgraded 2 sites from 0.7.3 to 0.8.2 that the menu structure got mixed up. On both conversions the display of item 7 was gone from the menu (content management and phplayers menu), in the database all was intact. Ended up deleting that item from the database and redoing that page in order to get it to display on the content management menu and the phplayers menu. Wasn't logical what was happening so never reported it as it was very difficult to describe in a useful way. On both websites this was a page with the News module being displayed.
Hope this info helps !
phplayers / start_element
Posted: Mon Jan 24, 2005 4:41 pm
by Ted
A content page with {cms_module module='News'}?
phplayers / start_element
Posted: Mon Jan 24, 2005 4:42 pm
by Greg
Yes, that was the only content.
phplayers / start_element
Posted: Mon Jan 24, 2005 4:51 pm
by Ted
Ok, I'll check that out as well when I do the 0.9 bug fixes (still working on the API conversion at the moment).
phplayers / start_element
Posted: Tue Jan 25, 2005 7:28 am
by user667
Hi again,
Thanx for your replies.
Since my problem is considered a bug - is there a possible way to work around it until the next release (hopefully featuring a bugfix
)?
phplayers / start_element
Posted: Wed Jan 26, 2005 2:24 am
by Ted
I have this fixed in svn, however, it's in the ported version for 0.9, so it wouldn't be real easy to port back to 0.8.2. If you're really stuck, I can try, or if it can wait for 0.9, then all the better...
phplayers / start_element
Posted: Wed Jan 26, 2005 11:59 am
by user667
is there a way to download the complete current svn tree?
i'm a complete noob concerning these things
i noticed that with the viewsvn.cmsmadesimple.org there's access to every file - but downloading all separately would be kinda stupid
and there' still the question if the unfinished version would be working ...
if there's no way for getting this to work, i'll be waiting calmly for the 0.9 release
anyway - thanks for the support
phplayers / start_element
Posted: Wed Jan 26, 2005 12:13 pm
by Greg
No hurry here wishy, after deleting and re-creating the News page all is functional.
phplayers / start_element
Posted: Wed Jan 26, 2005 12:34 pm
by user667
@Greg ... that's fine for you
I'm starting from scratch and need the feature working
phplayers / start_element
Posted: Wed Jan 26, 2005 1:00 pm
by Greg
Do you need the menu to start on a sub-menu item? or a main content item?
The parameter works if you use:
Code: Select all
{cms_module module="phplayers" start_element="2"}
But not if you use:
Code: Select all
{cms_module module="phplayers" start_element="2.1"}
phplayers / start_element
Posted: Wed Jan 26, 2005 8:44 pm
by user667
Greg, you're tha man
I'm absolutely sure that I tried using the "" for the setting, but obviously always with the wrong parameter (contentid, 2.1, .... )
damn I hate my brainlag
