kongondo

Update: Version 0.1.1 And, we are back! Thanks for waiting! Fixed bug relating to getLanguageValue() (issues #22 and #25). Thanks @all who reported, tested,and fixed the issue. Fixed bug where 'has_children' would not be applied to a menu item whose children were included 'natively'. Switched to $this->wire('pages') from wire('pages') (and similar). As per request at issue #18, added option 'default_class' to enable application of a default CSS class to every menu item at API level. Thanks @jlahijani. You can use this API-level option to add custom CSS class(es), e.g. Bootstrap or Foundation ones.

They don't have to be configured as hidden/unpublished. It all depends on your use case. You may want to show them (i.e.. Year, Model, etc) as menu sub-dividers for instance. Other than hiding them, If you don't want them to show up in menus, you could also remove them from the returned PageArray prior to outputting your menu.

Don't know if that is possible (I know one can view their liked content though)...How about doing it the 'old-fashioned' way, ctrl-D . I do that often (not just bookmarking threads but posts as well) but also use SearchMark to search through contents of my bookmarks. Edit: Welcome to PW and the forums

Useful to know: http://processwire.com/api/arrays/

Worked as expected in my testing (PW 2.7.2). Are you getting any errors? Btw, you are naming your fields using upper-case first letters? It still works but it's a good idea to follow the recommendation about naming fields:

Seems you got your modules confused This is the module you want: https://github.com/ryancramerdesign/MarkupLoadRSS. MarkupLoadRSS: It reads feeds. http://mods.pw/W What you have above (part of the core) is: Markup RSS Feed. It generates feeds. Install #1 and you should be fine. I tested your code and it works.

I am guessing both since ProFields will continue to work for both...

Whaa? ....I used Win10 for about 30 minutes and couldn't stand it. Switched back to 7

Previewing Audio & Video...

Or maybe search in a /site/somefolder/ first for a favicon and use that if one found?

Update: Version 4 Up on GitHub Changes In addition to the using a custom selector to filter for selectable page markers, you can now also use custom PHP Code. NOTE: (a) Custom PHP code will only work with the Asm Select page selector option. (b) Custom PHP code overrides custom selector if set Will submit to Modules Directory once I have done the README (might take a while...) ps: Updated first post to reflect current status...

Cool! I didn't have a chance to test in the frontend.

Update: Version 3 Unified markers working fine (thanks @heldercervantes) Fixed position differences between the 3 marker styles; (thanks @heldercervantes) Unified look, so that all marker styles feature the same kind of border and colors; (thanks @heldercervantes) Improved the way markers are highlighted; (thanks @heldercervantes) Added a higher z-index to the highlighted marker, bringing it on top of the others; (thanks @heldercervantes) Tweaked draggable event to remove the snapping that happened when user started dragging the marker. (thanks @heldercervantes) Callout markers display referenced page title instead of marker number Confirmed testing OK with Reno Theme Ready to grab from Github Pending: ReadMe/Docs...+ long coordinates table..

Done, works fine! Tested with Reno Theme as well (see screens). Thanks. Updating repo now... Reno Theme view

OK, done.

@heldercervantes, Brilliant! I have amended code with your changes. I am not sure about the 'Page Titles' on the callout and teadrop styles => long names are extending outside the 'red bounds'. See screens below and let me know what you think. I've added you as module co-author in the next version

? $page->parent; http://cheatsheet.processwire.com/?filter=parent See also: $page->parentID; $p = $page->parent;// here, $page->parent will give you the parent page object of the current page or nullpage if it does not have one echo $p->title; if($p->id == $someOtherID)// do whatever....

Thanks. I suggest we all work from the same unified markup.

Updated first post to show module's API.

Update version 2: Added Tear Drop and Callout marker styles (thanks @heldercervantes and @trp respectively) Using unified markup for all the styles (<div><span></span></div>) CSS styles still needs quite some work, especially for the new styles (to fit into the unified markup) Circular Markers (default...for now) See screenshot in post #1 Tear Drop Markers Callout Markers

No, they don't have links atm. ps: Am moving the last conversations to the module's support forum to avoid confusion

@tpr, looking at your callout example, we could even have a choice to show 'marker title' instead of 'marker number' if user selects 'callout' for their marker style..

Alternatively, markup could be rendered to suit the CSS style, not the other way round Edit: I think that would be easier actually. So, if using 'callout' style, we use 'callout' HTML, if using 'Gmap/tear drop' style, we use its unique HTML and the same for 'circular'.

You won't have to. It remembers contexts: What you want is either #2 or #3 below: In view mode, if you haven't searched for any media, if you click on 'edit mode' button, you will be taken to edit screen for the media type you were viewing, with the first media selected to edit. So, if in view you were on 'all' menu, you will be taken to 'all' in edit. If you were on 'image' in view mode, you will be taken to 'image' on edit mode. If in view, you'd searched for media and got back some results, if you then clicked on 'edit mode' button, you would be taken to the edit screen for only those found items, shown one media at a time with pagination. If you got back only one result in the search, you would be taken to the edit screen of only that result (without pagination of course) If in view mode you click on the title of a media, you will be taken straight to its edit screen, no questions asked See example GIF below In any of the above scenarios, clicking the view mode button will display the media you'd just edited. Edit mode: clicking on title of media in 'view mode' - (#3 above)

Sorry guys...Couldn't do this earlier and could not implement the latest marker designs (callout and tear drop [gmap]). CSS gave me a lot of grief so I stopped. Would appreciate if either of you could work out if/how all three marker styles could be available but still allow marker positions to remain in place, thanks! Started a support forum here: https://processwire.com/talk/topic/11863-module-imagemarker-fieldtype-inputfield/