2017 © Pedro Peláez
 

wordpress-muplugin wp-mu-s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

image

axelspringer/wp-mu-s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  • Friday, May 4, 2018
  • by axelspringer
  • Repository
  • 3 Watchers
  • 0 Stars
  • 4 Installations
  • PHP
  • 0 Dependents
  • 0 Suggesters
  • 0 Forks
  • 0 Open issues
  • 7 Versions
  • 0 % Grown

The Versions

04/05 2018

dev-master

9999999-dev https://github.com/axelspringer/wp-mu-s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  Sources   Download

Apache-2.0

wordpress muplugin

04/05 2018

2.0.0

2.0.0.0 https://github.com/axelspringer/wp-mu-s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  Sources   Download

Apache-2.0

wordpress muplugin

20/07 2017

1.0.4

1.0.4.0 https://as-stash.axelspringer.de/projects/WPMUP/repos/s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  Sources   Download

proprietary

wordpress muplugin

02/06 2017

1.0.3

1.0.3.0 https://as-stash.axelspringer.de/projects/WPMUP/repos/s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  Sources   Download

proprietary

wordpress muplugin

02/06 2017

1.0.2

1.0.2.0 https://as-stash.axelspringer.de/projects/WPMUP/repos/s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  Sources   Download

proprietary

wordpress muplugin

31/05 2017

1.0.1

1.0.1.0 https://as-stash.axelspringer.de/projects/WPMUP/repos/s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  Sources   Download

proprietary

wordpress muplugin

24/04 2017

1.0.0

1.0.0.0 https://as-stash.axelspringer.de/projects/WPMUP/repos/s3-postmeta-patch

Images that are not uploaded over the wordpress backend don't have a 'amazonS3_info' entry in the database. We have to make sure, this info exists. Otherwise we are running into unexpected side effects.(e.g. images are not displayed properly in the text-editor)

  Sources   Download

proprietary

wordpress muplugin