@jdaviescoates Thank you!

@privsec I'm currently trying the custom integration approach. But, I'm unable to obtain the fully rendered html for the email that Ghost natively delivers in the newsletter.

@jdaviescoates I only wish I knew why. 🔌

Good suggestions, made the changes.

@jdaviescoates thanks, that makes sense. I have added it.

I don't actually think any php code will be run within the Ghost app, unless Ghost itself would call the php interpreter. Ghost is a nodejs application.

@girish

Yes I did. I bumped the memory limit to 4096, in the ENV file and in the Cloudron admin panel for the app.. I upgraded my linode to 8GB of Ram too, just for this.

Solution: increase both poste & my SQL database memory limit in Cloudron services tab, to 2GB each. Reverted back to default after import

I then restarted the entire server, and began the process of importing.

it then worked!

@girish May I suggest to include the solution in the documentation for importing. This was a fairly large import with nearly 4K posts.

How do I flag this as solved?

@nj thanks, I have pushed the update.

@girish So, after updating for recent versions, my main.yaml file looks like this:

name: Deploy Theme on: push: branches: - master - main jobs: deploy: runs-on: ubuntu-20.04 steps: - uses: actions/checkout@v3.0.2 - uses: TryGhost/action-deploy-theme@v1.6.1 with: api-url: ${{ secrets.GHOST_ADMIN_API_URL }} api-key: ${{ secrets.GHOST_ADMIN_API_KEY }}

I've also renamed the Github repository to:

Basho-master--34-

so that it matched the theme name on Ghost admin:

basho (Basho-master--34-) Version 2.3.0

On every commit, the "deploy" action is triggered. There is an extensive log, where the only issue is the "canary" version parameter copied above. Otherwise it announces a successful upload, but my theme files are not updated. I'm not sure where the repo gets uploaded, I guess...

Unmodified themes will update automatically since it's part of the upstream code.

@jdaviescoates good idea!

Seems it would require some hacking to get working in Ghost, a good suggestion for the upstream devs.

The API seems mostly undocumented, hence would be useful to know if they followed a particular pattern of another API mail provider.

@kris X-Forward-For header is already set, can you use that instead?

@fbartels Thanks, guessed as much. Something we'll need to have a think about.

@jdaviescoates Oh, it was made available to all only yesterday. So, probably takes a couple more days to actually auto-update.

@abargel Well, actually, from the MySQL access in Web terminal, and a little help from the MySQL manual, it wasn't that difficult to find the table with
SHOW TABLES;
then
SELECT * FROM members_stripe_customers_subscriptions;
and add records with information from Stripe (and from the table members_stripe_customers) with
INSERT ... VALUES (see MySQL manual for format)

Sure, it is a bit tedious... But for a limited number of members, it can be done 😉

ok thank you wait and see then...

@girish said in Enable enableDeveloperExperiments:

enableDeveloperExperiments

moving it outside privacy worked, thank you!

@girish that was an amazing wild guess 😏

@kaxline if you can post the final solution, it will be findable by others later. 🙏

Interesting fix - https://github.com/docker-library/ghost/pull/281/commits/a3981512d2f9e368d75b97b2f80db91a97dfcff4 . They downgraded python to make it build properly.

@girish I struggled with this for ages then gave up, will give it another go now, thanks!

@girish thanks. Will try it out.

@robi thanks, will keep in mind. It has at least one major flow: I will also have to rewrite the links in the articles and they won't work in WYSIWIG anymore.

With this said, I would rather have a proper solution, as opposed to that kind of work-arounds.

@tshirt-chihuahu It should rarely happen (but it happens). I will put the workaround in the package itself. It seems that workaround works quite reliably for a couple of years now.

@nebulon For me, no. I downgraded, then reupdated and it worked.

@robi said in Docuhub Theme:

That's not OSS

I think in regards to this Docuhub theme you are correct. I don't see anything about it being open source and so am confused as to why @marcusquinn described it as such.

But with regards to things like StudioPress themes IncSub plugins etc, it's perfectly feasible (and in the WordPress world very common) for people to charge for open source programs. There is nothing in the definitions of Free Software nor Open Source definitions that says you can't do this.