heldercervantes

My hosting provider says they've ran the chown command and that didn't fix it, so... McGyver time! I just duplicated the whole "site" folder with php. I took this script and slapped it in a php file, then temporarily changed public_html permissions to 777 and ran the script copying "site" to "siteB". Every file and folder in siteB got the correct owner/group. Turned permissions on the root folder back to 750 and renamed "siteB" to "site". Done.

Thanks for pointing me in the right direction guys. I suck at SSL, never even touched it. Now in my support ticket it looks like I actually know what I'm talking about

I'm going through this problem on my end as well. The Dolce Vita website uses multisite to manage multiple malls under the same PW installation. Now I separated 3 malls to a second installation, basically just downloaded the whole site into my computer, cleaned up, and re-uploaded to a new hosting. Now editing a page I get this error in every image field. Setting permissions to 777 seems to work, but leaving it like that scares me. Seems apache is unable to write over files/folders created by FTP upload. Any way to get around that without nuking the whole thing?

I'm having the same issue Guy Verville had. Downloaded a website from production to local, imported the database, changed mysql authentication on config.php (checked it thrice) and the same error occurs. Nothing on errors.txt, and changing debug to true adds nothing to the message. I also changed permissions of everything to 775. Nothing seems to work. I'm clueless. *EDIT* : Also tried invalid DB login info to see if something would change. Nothing. *EDIT 2* : Placing echos all over index.php I eventually narrowed it down and discovered the previous coder messed with the file. Problem fixed.

Implementing this on a new site I detected a couple of "nice to haves". Sorting X and Y fields would accept decimals for fine-tuning. Bigger maps get too small for precise positioning of markers, and rounded percentage can be insuficient on the front-end. For sorting, if anyone needs it, I managed to get around to an alphabetic sorting based on the referred page's title, like this: $dots = $page->mapDots; foreach ($dots as $dot) { $dot->sortname = $pages->get($dot->info)->name; } $dots->sort('sortname'); Though it would be cool to manually sort markers on the list, this approach lets you sort by any field, and probably even the pages position relative to its real parent (I think, didn't try).

Thanks LostKobrakai. I was assuming = meant exact match.

Hi guys. Can't find this info anywhere. I'm trying to use the multipage values to do a search function. There are tours on this project, and location of options on a via page select. Like tags: "downtown, old town, beach...". On the search field, the admin selects one or many. On the frontend, the user can select whichever wanted, and output tours that have at least those options selected. My query looks like this: template=tour, (where~=1041 || where/~=1042) But it doesn't understand the ~= How do I get around this? thanks, H

Hey guys. I'm submitting my latest project to the directory. http://www.sagatex.pt Sagatex represents fashion and sportswear brands in Portugal, such as Fred Perry, Diadora, Dr. Martens, etc. This site features a product catalogue and a store finder. I like keeping my ingredients to a minimum. Here, I used: Reno theme InputfieldRepeater InputfieldMapMarker MarkupSEO ImportPagesCSV Enjoy

Well in my case the image field doesn't display the edit button when inside a repeater. When outside the repeater, the button appears. What gives?

OF COURSE! I was searching from $pages and completely forgot you could do it from a $page. Big thanks! Now excuse me while slap myself in the face for a moment.

Hi guys. This is probably real easy and my headache is probably keeping me from thinking straight. Take a products catalogue. The sections have multiple levels, 3 in my case. At the end of each branch there are products. So when I'm at a top section, I want to display all products under all child sections, grandchild sections and so on. How do I reference this in the selector? My only idea is to recursively check every child page down the tree where 'template=section' and slap each of them on the selector, but it seems wrong.

This is the site that prompted making this module. It's still in development and this link will die eventually: http://jacinto-lda.com/2016/pt/empresa/internacional/ Here's the abridged code from the template: <img src="<?= $page->images->first->url ?>" class="worldMapImage"> <div class="dotsList"> <?php foreach ($page->map as $dot) { $dotPage = $pages->get($dot->info); echo '<div class="dot" style="left:'.$dot->x.'%; top:'.$dot->y.'%"></div>'; } ?> </div> I have a few more things in there for generating the hover info, making some dots red and so on, but I cut that out to keep the example simple. You probably need to change $page->images and/or $page->map to suit the field names you're using. And of course this needs proper CSS to display correctly, but you can inspect those from the link if you're having trouble. Hope this helps.

Does this still happen if you have more than 1 marker?

Same here. When we built it I was testing on 2.7.2 When I started that project I began on PW3 but there were other modules misbehaving, so I went back to the master version. I suggest you do the same.

Updated to the latest version to test callouts. Looks great. With short names as in this particular use case, callouts greatly improve usability. BTW, should probably update the description on the first post in this thread: "one can only choose from one type of marker (circle) at the moment". No longer the case.

Well that took me a lot less time to implement than it did to add the content I needed for testing it out. Worked like a charm, didn't need any tweaking at all. The only thing I noticed missing was the keyboard fine-tuning. But that would conflict with Reno theme's expanding / collapsing of the left column, so best leave it as it is. In this case, on the frontend I have a rollover behavior that pops up an info box on each spot. The box pops to the right, so I'd have a problem with the ones closer to the right edge. But since the module returns % based positions, I can easily add a CSS class whenever the dot is over 50% horizontal, to make the popup appear to the left instead. The filtering options for the page selector also worked great. Limited that to a specific template and voilá. On the image below you'll see I have white and red dots on the frontend. Those are according to the parent of each dot. Easy as pie. Great work @kongondo. Here's a side by side of the field, and the end result:

Ok, maxwidth was playing pranks. Just add these couple of lines: max-width: none; white-space: nowrap; in the "div.callout span {" statement on line 142, and names should show up nice on the callouts.

I meant numbers on the teardrops and names on the callouts But I see from your GIF that it's getting line breaks. I only tested with single words and didn't notice it was doing that. But it's an easy fix. Give me a sec.

@kongondo, just made a little tune-up on your code: Affected files: InputfieldImageMarker.css InputfieldImageMarker.js Changes: Fixed position differences between the 3 marker styles; Unified look, so that all marker styles feature the same kind of border and colors; Improved the way markers are highlighted; Added a higher z-index to the highlighted marker, bringing it on top of the others; Tweaked draggable event to remove the snapping that happened when user started dragging the marker. Suggestion: Callout and teardrop styles seem redundant. I suggest that on callout style, instead of the number, we show the page name. CSS is ready for this change, just output the name in the span and it expands from the center. You can find the update here: heldercervantes.com/experiments/ifim/FieldtypeImageMarker_2.zip I'm starting to implement this on a website right now. It will be a good testing ground. First impressions are good, second impressions coming soon.

@kongondo Got a preliminary version I can test drive? I'm almost done building the website and need to put something together for that section. If not, I'll just slap in there a couple of fields for x and y.

Sounds great BitPoet. Looking forward to the updates. IMO this feature is essential for multi language sites, and I'm sure I'll be using in basically every project I make. It's weird that this didn't generate more response from the forum. Please update this thread when you release a new version.

This looks cool and I have this need in just about every site I make. But I find it strange that this post is a year old and module isn't listed on the modules directory. Does that mean there are other modules / approaches to this problem? EDIT: Looks like I've jumped the gun there. Just seen it's in alpha stage on github. Bummer, alpha is scary for client work.

I've updated it on the original link: http://heldercervantes.com/experiments/ifim/ Added a behavior for turning the last marker green when clicked/dragged, and tested one with 999 for the number. Don't think anyone will ever need more than two digits though. I'm on a mac and don't have a pc for proper cross-browser testing, so let me know if you detect any problems. EDIT: Re-uploaded file after adding a little keyboard control, complete with shift-key for 10px skips.

Check this out for the marker: http://www.heldercervantes.com/experiments/ifim/marker.html Pure CSS; Minimal markup, just the marker div with inline left and top position (can be % of course) and a span surrounding the number; The main marker div is just 1x1 pixels making the position accurate; Bubble is a ::before pseudo-element; Features active state just by adding/removing css class; Used plain red and green for colors. Can this be read from the theme's colors?

Where else would someone post a question like I did, and in the same day find people gathering around the subject and build a new module that solves the problem? This forum feels like actually being in a room filled with people who know their stuff and are willing to help a brother out.