Nothing after clicking Next on Gallery Source

Can you check your JavaScript console (Ctrl + Shift + I in Chrome) and let me know if you see any errors? If you are seeing an error, can you let me know what it is? Also, if the error over there has the code 500, can you check your server logs and see if you are finding any errors there?

Without the errors it is next to impossible for me to troubleshoot the issue, but I can give you a workaround if you aren’t able to find the errors.

Thanks for the quick response! I get these errors show up

JQMIGRATE: Migrate is installed, version 1.4.1
?v=2.0:6 WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403
v @ ?v=2.0:6
load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,quicktags,moxiejs,plupload&ver=c458f9e5e564ace4edfdcb351553bba3:9 JQMIGRATE: Migrate is installed, version 1.4.1
/blog/wp-admin/admin-ajax.php:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
?v=2.0:6 WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403
v @ ?v=2.0:6
?v=2.0:6 WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403
v @ ?v=2.0:6
_ @ ?v=2.0:6
o @ ?v=2.0:6

so 403 and 500

Nothing listed on my server under “errors” in cpanel

The 403 error is not from Photonic – that is coming from WP itself (see https://github.com/Automattic/pinghub/issues/8). What I am not sure though, is if it is resulting in the 500 error on Photonic.

Do you have access to your server logs? Typically these would be be in your WP installation (your hosting provider might be able to point you to it). The error log would have messages specific to Photonic. Those messages will point me to the root cause.

Does the error show up instantly or does it take time? One cause for 500 errors is if a PHP file is inaccessible, but again, the only way to find out is by looking at the log.

This is the second report of a 500 error that I am receiving in the past 1 week (I haven’t had any prior to this). That is why I would like to get it resolved for good. I can give you an alternative to create your shortcodes (see documentation links for Google albums and photos, and Instagram), but the interactive shortcode builder is a lot easier to use.

Hmm the 403 even shows up on the main wpadmin page actually.
the 500 shows up right after I hit the next button

i tried
[photonic type=’google’ view=’albums’ access=’shared’]

and this worked, showed my shared albums/singles

Is this what you mean? Looking inside “error_log” inside the WP folder I see PHP errors, for other plugins. I just tried deactivating it and I still get the problem though.

[11-Jan-2019 01:31:18 UTC] PHP Warning:  html_entity_decode() expects parameter 2 to be long, string given in /home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/admin/class-nelio-content-post-helper.php on line 388
[11-Jan-2019 01:31:18 UTC] PHP Warning:  html_entity_decode() expects parameter 2 to be long, string given in /home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/admin/class-nelio-content-post-helper.php on line 387
[11-Jan-2019 01:31:18 UTC] PHP Warning:  html_entity_decode() expects parameter 2 to be long, string given in /home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/admin/class-nelio-content-post-helper.php on line 388
[12-Jan-2019 04:06:52 UTC] PHP Fatal error:  Call to undefined function is_plugin_active() in /home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/includes/compat/pagefrog.php on line 27
[12-Jan-2019 04:06:53 UTC] PHP Warning:  require_once(/home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/includes/utils/nelio-content-missing-wordpress-functions.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory in /home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/includes/class-nelio-content.php on line 501
[12-Jan-2019 04:06:53 UTC] PHP Fatal error:  require_once() [<a href='function.require'>function.require</a>]: Failed opening required '/home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/includes/utils/nelio-content-missing-wordpress-functions.php' (include_path='.:/opt/alt/php53/usr/share/pear:/opt/alt/php53/usr/share/php:/home/barnz2k/public_html/blog/wp-content/plugins/background-manager/vendor/OAuth/lib') in /home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/includes/class-nelio-content.php on line 501
[12-Jan-2019 04:09:09 UTC] PHP Fatal error:  Call to undefined function is_plugin_active() in /home/barnz2k/public_html/blog/wp-content/plugins/nelio-content/includes/compat/pagefrog.php on line 31

hmm, I just updated my PHP version from 5.3 to 5.5 to fix an error on another plugin, and now the add media seems to work!

separate question – where does that album ID come from? Its not the same as the link when viewing the album or the share link.

hmm, I just updated my PHP version from 5.3 to 5.5 to fix an error on another plugin, and now the add media seems to work!

That is really interesting. At least it provides me with something that I can pass on to other users as a suggestion.

I would have suspected the fatal errors from Nelio to be causing the issue, as its requirement states that it needs PHP 5.4. Let me work with these pointers and play around a bit.

separate question – where does that album ID come from? Its not the same as the link when viewing the album or the share link.

That is returned by the Google API. It is a unique type of representation, where Google first uses this id to generate a bunch of short-lived shortlinks, each of which then points to the actual album or photo. The shortlink is what you see in the markup; as it is only valid for around 30 minutes you cannot use a caching plugin.

I am marking this resolved, but I will continue looking into the PHP 5.3 issue.