EasyPopulate 4.0 Support Thread

[Feznizzle]

Hey MC!

Way back on post #2800, you mentioned adding the ability to export category paths for informational purposes. Then, in the very next post, I was able to find some code on github to get that working.

It was extremely useful to me and, now that I'm building a new site, I'd really like to add that ability in to my EP4 install. Sadly, I cannot seem to find that modification on github anymore.


Any chance you could remind where to find that?

Btw, I have a ZC154e with Easy Populate 4.0.36.ZC - 07-05-2016 installed.

[mc12345678]

Hey MC!

Way back on post #2800, you mentioned adding the ability to export category paths for informational purposes. Then, in the very next post, I was able to find some code on github to get that working.

It was extremely useful to me and, now that I'm building a new site, I'd really like to add that ability in to my EP4 install. Sadly, I cannot seem to find that modification on github anymore.


Any chance you could remind where to find that?

Btw, I have a ZC154e with Easy Populate 4.0.36.ZC - 07-05-2016 installed.

Well, I was doing some github "cleanup". In my opinion, there were too many branches and too many side things that either were or should have been in the master thread or should have been consolidated to apply to a single change instead of a spelling change here, a thing there, etc... If you need the specific change that was incorporated into the master thread: https://github.com/mc12345678/EasyPo...9cd7cb277f28d0

Otherwise, there are some other feature modifications and changes being applied (take a look at the Insights->Network to see sequencing and plan for incorporating) but only into the master thread once confirmed functional/non-disfunctional. Working towards issuing a new version based on some of the things pointed out here and some always wished were present features.

[Feznizzle]

First, HUGE THANKS! Awesome as always, thanks MC.

Second, I tried to check out Insights->Network but found nothing there. Thought maybe it was because I was looking at your fork, so I backed up and checked the other fork, still no dice.

[mc12345678]

First, HUGE THANKS! Awesome as always, thanks MC.

Second, I tried to check out Insights->Network but found nothing there. Thought maybe it was because I was looking at your fork, so I backed up and checked the other fork, still no dice.

Trying not to read anything into the "second". Ie. Did the direct link help get the functionality back that was desired? Perhaps - also under-expressed use of the insight->network portion. May I recommend taking your mouse cursor over areas such as the black dots on any line. Perhaps clicking on one to see what happens. Explore a little more. :) I know, have a job to finish. Be sure to stop and smell the roses once in a while. :)

[Feznizzle]

Yes, your direct link to the code was enough to get the desired functionality working. I was able to export category paths, no problem. Again, thanks.

I guess I'll let the Insights->Network go? I thought you guys were working on "other feature modifications and changes being applied" and you were inviting me to take a look at the plan. To see it, I was supposed to go to the github page for Easypop, click on Insights, then click on Network.

I did that, but found nothing and/or did not understand what I was looking at.

Here are two screenshots to show you what I could see:

.
.
.
.
.
.
.

[mc12345678]

Unfortunately the "map" of the network didn't come through on those screen shots, but the previous links took me to where I expected you to be and I would guess the lack of the map image is something related to github and screen capture. Regardless, yes the thought was to offer a sort of way to see the upcoming direction(s) of the plugin. Each dot on the line represents a saved change. There is a description that displays when hovering over the dot. Clicking on the dot opens a new window and takes you to the specific commit (change) that was made where you can see both the description, any comments, and the specific code changes to support that change.

Previously I believe you had been able to find that specific change because I had created a separate branch the name of which clearly described the intended change. That branch had multiple commits in it (more than one file was modified and modifications were done online instead of from a computer where more control can be had on how the changes get saved). All of those changes were summarized into the one commit to which I directed you. It can be found in the "dots" before the end of master.

Another reason to send to the network is because there are multiple little branches that I ended up stacking into a single chain. I expect that I will be able to confirm each chain off of the master one by one and then merge that change directly into the master branch. Thus, if you were to go to the last branch, you would see how the software is expected to be configured to reflect as if all changes were incorporated. I have thought of a few changes made that I want to let up on to support how others have likely built off of EP4 and not require them to make changes in support of some upcoming export features. Plus I haven't completed the matching import changes to some of that, so they may get bumped a little. Doesn't do a lot of good if can't import what has been exported. :)

So ignore or not, can do either. I know there was a date related issue that you had identified and I at least attempted to correct, though I'm still testing import aspects (having to be sure I have a backup/restore path for the database before doing that).

Sorry for removing that branch, but like I said was getting too "busy" for my tastes and management of ensuring nothing was left off/out.

[Feznizzle]

MC, I'm always supper grateful for the work you do on this mod. So no worries about killing that branch!

I now have a copy of it on my computer. If the category-path export doesn't make it into a future update, I should be able to just slip into my own install using what I now have.

Btw, I opened github in a dif browser and the info you where alluding to popped right up. Sorry about that, sometimes I forget that my dev browser is stripped down!