Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Previously posted at https://github.com/wet-boew/wet-boew-drupal/issues/1830
After a fresh install (now 3 fresh installs) ENTITIES DEPLOYMENT under the deployment section is currently broken. Only the tabs appear. Has anyone else encountered this?
Comment | File | Size | Author |
---|---|---|---|
#17 | Deployment.jpg | 198.08 KB | webpaving |
Comments
Comment #2
sylus CreditAttribution: sylus commentedI need a bit more information in order to be able to debug this.
1) What exact version are you using? 4.6 or 4.x?
2) Exact reproduction steps (no step to small to list)
3) Are you seeing any JS errors in the console?
4) What browser are you using?
We are successfully using 4.6 across many environments all using the deployment method.
On my personal development environment I am always using latest dev and also can't seem to currently reproduce this problem.
Also to just be sure your simply stating that the view isn't rendering completely?
Comment #3
sylus CreditAttribution: sylus commentedComment #4
kmtremblay CreditAttribution: kmtremblay commentedSorry about that, frustration is slowing down the ol' brain lol.
The view is rendering, I can see it for a fraction of a second. It then vanishes and the tab labels are clickable but do nothing.
Comment #5
sylus CreditAttribution: sylus commentedHow are you enabling deployment modules? You should only have to do:
and all the dependencies should be enabled.
I think that might be your problem. Perhaps one of the dependencies for that screen wasn't enabled properly.
Comment #6
sylus CreditAttribution: sylus commentedAlso you shouldn't need to be doing your own makes if not developing; the full build is already present @ drupal.org/project/wetkit.
Comment #7
sylus CreditAttribution: sylus commentedHere are my steps:
1) Download tarball from drupal.org/project/wetkit (I use drush make as developing)
2) Install:
drush si wetkit \
wetkit_theme_selection_form.theme=wetkit_bootstrap \
install_configure_form.demo_content=TRUE \
--sites-subdir=default \
--account-name=admin \
--account-pass=WetKit@2015 \
--site-mail=admin@example.com \
--site-name='Web Experience Toolkit' \
--db-url="xxx" \
--yes;
3) Enable deployment (source side)
drush --root=/data/var/www/wxt.gov en wetkit_deployment_source -y
4) Go to url:
http://wxt.gov:8000/en/admin/structure/deploy
5) No problems with quicktabs screen.
----
Here is what got enabled by wetkit_deployment_source:
Comment #8
kmtremblay CreditAttribution: kmtremblay commentedThank you for the reply, Sylus, I'll give that a shot once I get into the office tomorrow.
I'm willing to bet money that I messed something up with the dependencies, I was enabling them through the modules section.../winner
Comment #9
kmtremblay CreditAttribution: kmtremblay commentedI've just restarted everything from scratch following your directions. I am still seeing the same behaviour with the view :(
The HTML for the view is in the inspector and there are no errors in the console. This is been consistent in Firefox and Chrome on both of our PCs and I have just experienced in in Safari on a macbook.
Output from drush en wetkit_deployment_source --yes
If Javascript is disabled then we are able to see it, otherwise IF it shows up it certainly disappears on a page reload or selecting one of the tabs.
Comment #10
sylus CreditAttribution: sylus commentedThis doesn't really make much sense to me as repro steps should get us to the same results ^_^. I have to assume something is incorrect related to the setup:
Under admin/reports/status there are no warnings?
Under recent logs there is nothing written?
Additionally you have:
php memory_limit set to 292MB
max_execution_time something higher then 180
----
I nor any of a few developers I reached out cant seem to reproduce this atm. I think a good way or proving whether this is setup related might be with the steps below (should take 10 mins total):
1) Go to: https://simplytest.me/project/wetkit/7.x-4.x
2) Install by just keep clicking next
3) After install go to admin/modules screen and enable wetkit_deployment_source (you might get an server error but can just refresh page as php memory + timeout for scripts is too low on simplytest)
4) Go to admin/structure/deploy and you should see everything working (despite earlier error)
Can you verify the above works for you?
Comment #11
natew CreditAttribution: natew commentedI just tried this with a fresh install of 4.6 and had no issue browsing to /en/admin/structure/deploy. Using similar instructions to what sylus provided.
This in my dev environment which is Ubuntu 12.04, Apache 2.2.22, MySQL 5.5.47,and PHP 5.3.10. This seems to be an issue specific to your environment?
Comment #12
kmtremblay CreditAttribution: kmtremblay commentedPHP Version is 5.6.19
Mysql Version is 5.1.73
CentOS Version is 12.3
php.ini settings are several times higher than the ones suggested now, they were lower but I am still getting the same results after reinstall.
I am running the installation on simplytest me and will report back asap :) Thanks again for the help.
Comment #13
kmtremblay CreditAttribution: kmtremblay commentedI installed the distro on simplytest.me twice, once with demo content and once without.
It works as expected with demo content enabled, but without it I reproduce my issue.
There are still no errors etc, but somehow the demo content is (seemingly) the key.
Comment #14
webpaving CreditAttribution: webpaving as a volunteer commentedI've been working with @ktremblay on this issue and would add that using 7-4.6 and the module-enabling approach recommended by @sylus we have deploy working like a charm via the content types like like "Deploy Simple" and "Deploy Moderated".
I just tested this approach using the build of 7-4.x from GitHub and was _also_ successful.
But, either way, some JavaScript is hiding that "Entities Deployment" tabs content (on second load) at ...
/admin/structure/deploy
... when we don't install WxT demo content.
Thanks for all your help.
Comment #15
sylus CreditAttribution: sylus commentedWhen you dont install demo content there is no content to display. If you manually added an entity translated (en + fr) piece of content, does it then show up? Glad we isolating the issue now.
Comment #16
sylus CreditAttribution: sylus commentedAdditionally you can also go here:
/en/admin/structure/quicktabs/manage/deployment_quicktabs/edit
Then unselect "hide empty tabs".
Comment #17
webpaving CreditAttribution: webpaving as a volunteer commentedThanks, Sylus.
When we deselect "hide empty tabs," the full widget appears, but it's not empty:
Comment #18
kmtremblay CreditAttribution: kmtremblay commentedThat's really...really strange. I wonder why Quicktabs thinks there is no content.
@Sylus, when I was testing, there was indeed content already created.
Comment #19
sylus CreditAttribution: sylus commentedThe only thing I can think is you didn't use Entity Translation to create the corresponding french node or the workbench state isn't set to published. Maybe take a look at the difference in demo content or just play around with the view to see which filter is affecting you:
en/admin/structure/views/view/deployment_administration_nodes/edit
I wonder if either of these bugs are related:
#2396031: quicktab is broken when empty tabs are hidden
#2577937: Allow Empty Tabs to Be Hidden in AJAX Mode
Comment #20
sylus CreditAttribution: sylus commentedI think there is some work to do with the hide empty tabs quicktabs provides. For now I am just going to disable that option as would rather display then view even if is empty rather then hide the whole tab.
The default will now be set hide_empty_tabs to FALSE.