search

inboundnow / inbound-pro

Inbound Pro Plugin for WordPress - Landing Page Framework, Calls to Action Framework, Visitor Analytics & List Segmentation, Email Campaigns & Marketing Automation
https://www.inboundnow.com
31 stars 17 forks source link

Inbound Pro Release #118

Closed atwellpub closed 8 years ago

atwellpub commented 9 years ago

For Pro let's:

I'd like to go ahead and start preparing the new site's database by getting all current membership holders imported into the new product, and get their license keys generated and displaying on their my account section.

The sooner we do this the closer we come to a public release.

@DavidWells I need your help in planning though. Is the inboundsite.wpengine.com database ready?

DavidWells commented 9 years ago

Sounds good. I can make the landing page.

inboundsite.wpengine.com DB is clean with only 12 users (blog post authors). It is missing the lastest blog posts too. I will need to import those.

I spent a bunch of time pruning old stuff out of the DB to keep it lean.

Do you know how to import just the paid membership holders without the extra crap from current inboundnow.com? Perhaps we just need to export their email addresses and programatically create the user accounts for them?

atwellpub commented 9 years ago

Yeah it will take some investigation. I'll get on it.

atwellpub commented 9 years ago

I forget, how are the license keys generated?

DavidWells commented 9 years ago

They are generated when a new user is created with an ajax call.

Also the current site is broken... Have you done anything to it recently? All landing page category posts are gone http://www.inboundnow.com/landing-pages/ did you change their categories or something?

On Tue, Oct 13, 2015 at 9:37 AM, Hudson Atwell notifications@github.com wrote:

I forget, how are the license keys generated?

— Reply to this email directly or view it on GitHub https://github.com/inboundnow/inbound-pro/issues/118#issuecomment-147770767 .

atwellpub commented 9 years ago

I haven't done anything since the last time I updated themes and plugins. And unless inboundly is pegged to a twentysomething template I don't think updating themes should have affected anything.

atwellpub commented 9 years ago
atwellpub commented 9 years ago

http://www.inboundnow.com/go/inbound-pro-registration/

Started the landing page, which could also serve as content for the welcome section inside the Inbound Pro plugin.

DavidWells commented 9 years ago

Ideally we would want something like this: http://stackoverflow.com/questions/9504791/is-there-anyway-to-programmatically-fetch-a-zipball-of-private-github-repo

Where github generates a tarball/zip that the customers download from a 'release' branch which has the latest stable version ( if this is master thats cool. We probably need to dev on a dev branch anywho)

On Tue, Oct 13, 2015 at 4:37 PM, Hudson Atwell notifications@github.com wrote:

http://www.inboundnow.com/go/inbound-pro-registration/

Started the landing page, which could also serve as content for the welcome section inside the Inbound Pro plugin.

— Reply to this email directly or view it on GitHub https://github.com/inboundnow/inbound-pro/issues/118#issuecomment-147884945 .

atwellpub commented 9 years ago

We've got the resources to do it on hand. I'll dig it up and get it installed. Be it a servelet or a method. Just have to look into it. Yeah we should dev everything on dev branch for all repos. We have to pick a point in time and agree to start doing it so we don't mix up standards. @daprela

Does the my account area on inboundsite support multiple domains if the package allows it? We'll need this too for those coming over and buying multi-site licensees.

Answered my own question, our API is built to handle and automatically add new domains: https://github.com/inboundnow/inboundnow.com/blob/master/wp-content/themes/inboundnow/functions/inbound-pro-api.php#L173-L178 and then they can edit them from the my account area.

atwellpub commented 9 years ago

@DavidWells we can use this link to get json data about the latest Inbound Pro download (includes a link to download)

http://inboundsite.wpengine.com/pro-api/pro/info?api-key=examplepublicapikey&site=http://inboundsite.wpengine.com

daprela commented 9 years ago

@atwellpub so that means that I must make any future pushes on the dev branch and not anymore on the master branch? The templates-landing-pages repo doesn't have a develop branch as of now, should I create it? This link https://github.com/inboundnow/inboundnow.com/blob/master/wp-content/themes/inboundnow/functions/inbound-pro-api.php#L173-L178 doesn't work

atwellpub commented 9 years ago

@daprela theoretically and in application yes, but we all have to agree right now to start working on dev branches immediately or else we will mix each other up.

I don't think we need to worry about working on a dev branch for the templates-landin-pages repository, only on these:

daprela commented 9 years ago

@atwellpub I'm working on a new email template right now, should I switch already to the dev branch? As an alternative, I will work without making any commits until you give me the ok (it's what I'm doing right now while I'm waiting for your answer)

atwellpub commented 9 years ago

Yes go ahead and switch I've made the switch too.

DavidWells commented 9 years ago

Whats the status on release?

I'd like to get the new site up and running within the next 2 weeks and start selling new templates w/ template acf plugin at least

atwellpub commented 9 years ago

There's a couple of things we need help on. I'm working on creating the grandfather system now, but these will need to be helped:

DavidWells commented 9 years ago

... I have a 500 server error from the latest inboundnow.com repo

Why?

I git reset to my last commit and my local instance works.

git reset --hard c4c57d5

This commit https://github.com/inboundnow/inboundnow.com/commit/c4c57d590901900869683ed7438a9d0310217f2b works fine locally

This is what I see from the latest master http://www.screencast.com/t/IF7yi91f1Rn

DavidWells commented 9 years ago

Found the issue. It is a Fatal error with yoastSEO. Looking into solution

DavidWells commented 9 years ago

" Fully explain our intentions concerning the inboundly site. Are we going to have two sites? Or one? This decision WILL affect internal code of Inbound Pro."

The idea is to keep the current site but have it under legacy.inboundnow.com and anyone that had purchased something from us before we turn on the new site can access their downloads from legacy.inboundnow.com

All new customers will use (new) inboundnow.com and inbound-pro to download there addons

DavidWells commented 9 years ago

"Link widget to link product pages to available relative documentation links (if we are serving them from new site, otherwise this will need to happen on the legacy site."

Documentation is going to get overhaul once new site is up and running. Everything will use the same master theme to keep things easier.

We can customize the new product pages with additional content areas once this happens

atwellpub commented 9 years ago

kk, if we keep legacy then we'll still want the small cosmetic issues addressed and 100%. For sales conversion and professionalism sake.

DavidWells commented 9 years ago

No sales will happen on old site. Only new site

On Nov 5, 2015, at 1:56 PM, Hudson Atwell notifications@github.com wrote:

kk, if we keep legacy then we'll still want the small cosmetic issues addressed and 100%. For sales conversion and professionalism sake.

— Reply to this email directly or view it on GitHub.

DavidWells commented 9 years ago

Old site is only for old users to download there individual assets

On Nov 5, 2015, at 1:56 PM, Hudson Atwell notifications@github.com wrote:

kk, if we keep legacy then we'll still want the small cosmetic issues addressed and 100%. For sales conversion and professionalism sake.

— Reply to this email directly or view it on GitHub.

atwellpub commented 9 years ago

Related Issue: https://github.com/inboundnow/inbound-pro/issues/122