Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

episode editor: podlove-admin.js: podlove_vue is not defined #1265

Closed
oe1rfc opened this issue Jan 23, 2022 · 3 comments
Closed

episode editor: podlove-admin.js: podlove_vue is not defined #1265

oe1rfc opened this issue Jan 23, 2022 · 3 comments
Labels

Comments

@oe1rfc
Copy link

oe1rfc commented Jan 23, 2022

Expected behavior

The Episode editor should load without JavaScript errors and Episode infos (title, etc) should be saved when saving the Episode.

Actual behavior

The following JS initialization error is logged in the browser console and none of the fields under Podcast Episode under the Episode Block/Classic Editor saved when saving the Episode, also media assets are not scanned. We suspect that the problem occurred after the update to v3.7.0.

Uncaught ReferenceError: podlove_vue is not defined
    at Object.beforeSend (podlove-admin.js?ver=3.7.0:1)
    at Function.ajax (load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=5.8.3:2)
    at Function.s.ajax.s.ajax (load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=5.8.3:5)
    at Object.h.ajax (backbone.min.js?ver=1.4.0:2)
    at Object.h.sync (backbone.min.js?ver=1.4.0:2)
    at n.sync (wp-api.min.js?ver=5.8.3:2)
    at n.fetch (backbone.min.js?ver=1.4.0:2)
    at n.initialize (wp-api.min.js?ver=5.8.3:2)
    at n.h.Model (backbone.min.js?ver=1.4.0:2)
    at new n (backbone.min.js?ver=1.4.0:2)

The global podlove_vue object is availaible in the console, but I assume that it's not initialized at the time when podlove-admin.js is loaded.

There is also an additional error with a GET request to wp-json/podlove/v1/shownotes when adding a new Epsiode, I suspect that this might be an aftereffect of the JS initialization problem, but I'm not entirely sure:

load-scripts.php: GET https://www.desperatehousehackers.net/wp-json/podlove/v1/shownotes?episode_id= 400 (Bad Request)
app.js?ver=3.7.0:2 could not load shownotes: Ungültige(r) Parameter: episode_id

System information (see Podlove > Support menu)

Website                    https://www.desperatehousehackers.net
PHP Version                7.4.27
WordPress Version          5.8.3
WordPress Theme            Kadence Child v1.0.0
Active Plugins             
           - Podlove Podcast Publisher v3.7.0
           - Podlove Subscribe Button v1.3.7
WordPress Database Charset utf8mb4
WordPress Database Collate 
Publisher Version          3.7.0
Publisher Database Version 153
Web Player Version         player_v5
Monolog Version            1
open_basedir               ok
curl Version               7.64.0
iconv                      available
simplexml                  ok
max_execution_time         30
upload_max_filesize        512M
memory_limit               256M
disable_classes            
disable_functions          pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
permalinks                 ok (/%postname%/)
podlove_permalinks         ok
podcast_settings           ok
web_player                 ok
podlove_cache              on
assets                     
  - mp3    audio/mpeg       https://www.desperatehousehackers.net/feed/mp3/
  - chapters.txttext/plain       no feed
cron                       ok
duplicate_guids            ok

0 errors
0 notices
Nice, Everything looks fine!
@eteubert eteubert added the bug label Jan 24, 2022
@eteubert
Copy link
Member

Thanks for the report, I'll work on a hotfix.

eteubert added a commit that referenced this issue Jan 24, 2022
@eteubert
Copy link
Member

I haven't been able to reproduce this but I have an idea why it might happen (sometimes?). See if 3.7.1 fixes it for you, should be available in a few minutes.

@oe1rfc
Copy link
Author

oe1rfc commented Jan 26, 2022

Hi, thank you for the fast fix, I can confirm that the initialization problem is fixed, I guess it might have always occured for me because I disabled caching in the Chromium debug tools. The initial problem that episode settings are not saved persists, but I can actually see the values in the save POST request, this seems to be a different problem with this instance. I'm closing this issue, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants